CVE-2026-95607

WPLMS Learning Management System for WordPress, WordPress LMS <= 4.973 - Authenticated (Subscriber+) SQL Injection

2026-10-02 08:55
Rafie Muhammad

Strategic Overview

Status
Patched in 4.974
Affected Version
<= 4.973
CVSS
6.5Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-95607
View all WPLMS Learning Management System for WordPress, WordPress LMS vulnerabilities

At a glance

CVE-2026-95607 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WPLMS Learning Management System for WordPress, WordPress LMS WordPress theme, affecting versions <= 4.973. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.974; sites on affected versions should update now. Disclosed October 2026, reported by Rafie Muhammad.

Vulnerability Overview

The WPLMS Learning Management System for WordPress, WordPress LMS theme for WordPress is vulnerable to SQL Injection in all versions up to, and including, 4.973. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in WPLMS Learning Management System for WordPress, WordPress LMS <= 4.973 takes an account at Subscriber level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WPLMS Learning Management System for WordPress, WordPress LMS the fix is 4.974: builds <= 4.973 are affected, anything from 4.974 onward is not.

Remediation

Update to version 4.974, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPLMS Learning Management System for WordPress, WordPress LMS 4.974 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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