CVE-2025-58668

WPLMS <= 4.970 - Missing Authorization

2025-09-22 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 4.971
Affected Version
<= 4.970
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-58668
View all WPLMS Learning Management System for WordPress, WordPress LMS vulnerabilities

At a glance

CVE-2025-58668 is a medium-severity Missing Authorization vulnerability in the WPLMS Learning Management System for WordPress, WordPress LMS WordPress theme, affecting versions <= 4.970. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 4.971; sites on affected versions should update now. Disclosed September 2025, reported by Rafie Muhammad.

Vulnerability Overview

The WPLMS theme for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to, and including, 4.970. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in WPLMS Learning Management System for WordPress, WordPress LMS <= 4.970 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WPLMS Learning Management System for WordPress, WordPress LMS the fix is 4.971: builds <= 4.970 are affected, anything from 4.971 onward is not.

Remediation

Update to version 4.971, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WPLMS Learning Management System for WordPress, WordPress LMS 4.971 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C