WordPress LMS theme <= 9.2 - SQL Injection Vulnerability

Successful exploitation of this SQL Injection vulnerability could grant an attacker unauthorized access to the underlying database. This could lead to the exfiltration of sensitive user data, including usernames, passwords, and personal information. Furthermore, an attacker might be able to modify or delete data, potentially disrupting the functionality of the LMS system. The blast radius extends to any data stored within the database accessible through the vulnerable query. While no specific real-world precedent is immediately apparent, SQL Injection vulnerabilities are consistently among the most exploited web application flaws, often leading to significant data breaches.

WordPress sites utilizing the LMS LMS Theme, particularly those running versions 0.0.0 through 9.2, are at significant risk. Shared hosting environments where multiple websites share the same database are especially vulnerable, as a compromise of one site could potentially impact others. Sites with weak database access controls or inadequate input validation practices are also at increased risk.

• wordpress / composer / npm:

grep -r "SELECT .* FROM" /var/www/html/wp-content/themes/lms/

• generic web:

curl -I https://your-wordpress-site.com/lms/vulnerable-endpoint?param='; DROP TABLE users; --

• wordpress / composer / npm:

wp plugin list --status=inactive | grep lms

1. 2025-07-04Disclosure

   disclosure

1. 已保留2025-06-19
2. 发布日期2025-07-04
3. 修改日期2026-04-28
4. EPSS 更新日期2026-03-23

The primary mitigation for CVE-2025-52833 is to immediately upgrade the LMS LMS Theme to version 9.3 or later. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) with rules to detect and block SQL Injection attempts targeting the vulnerable endpoints. Input validation and parameterized queries should be implemented in any custom code interacting with the database. Regularly review database access permissions to limit the potential impact of a successful attack. After upgrading, confirm the vulnerability is resolved by attempting a SQL Injection payload on the affected endpoint and verifying it is properly sanitized.