Debug Log Manager <= 2.5.2 - Unauthenticated Stored Cross-Site Scripting via 'log_js_errors' AJAX Endpoint
Strategic Overview
- Status
- Patched in 2.5.3
- Affected Plugin
- Debug Log Manager – Conveniently Monitor and Inspect Errors
- Affected Version
<= 2.5.2- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation
- CVE
CVE-2026-120114
At a glance
CVE-2026-120114 is a high-severity Improper Neutralization of Input During Web Page Generation vulnerability in the Debug Log Manager WordPress plugin, affecting versions <= 2.5.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.3; sites on affected versions should update now. Disclosed October 2026, reported by Josef Azizov (Spoofable).
Vulnerability Overview
The Debug Log Manager – Conveniently Monitor and Inspect Errors plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'message (and pageUrl)' parameter in all versions up to, and including, 2.5.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that the site administrator has debug logging enabled with JS error logging active, and that the attacker can obtain the publicly emitted dlmVars.jsErrorLogging nonce — which is broadcast on every frontend page — to pass the nonce check on the unauthenticated endpoint.
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 privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation
Reaching this weakness in Debug Log Manager <= 2.5.2 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Debug Log Manager the fix is 2.5.3: builds <= 2.5.2 are affected, anything from 2.5.3 onward is not.
Remediation
Update to version 2.5.3, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Debug Log Manager 2.5.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Debug Log Manager – Conveniently Monitor and Inspect Errors
- 5.4CVE-2024-35669: Debug Log Manager <= 2.3.1 Missing Authorization
CVE-2024-35669 - 5.3CVE-2026-9016: Debug Log… Improper Output Neutralization for Logs
CVE-2026-9016 - 5.3CVE-2023-6383: Debug Log Manager Directory Listing to Info Disclosure
CVE-2023-6383 - 4.3CVE-2024-33915: Debug Log Manager <= 2.3.1 Missing Authorization
CVE-2024-33915 - 4.3CVE-2023-5772: Debug Log Manager <= 2.2.0 Cross-Site Request Forgery
CVE-2023-5772 - 4.3CVE-2023-6136: Debug Log Manager <= 2.2.1 Missing Authorization
CVE-2023-6136
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C