CVEsqriousladCVE-2026-9016Published Jun 6, 04:28 · Updated Jun 6, 11:41 UTC
5.3
MediumCVSS 3.1 · from Wordfence
CVE-2026-9016

Debug Log Manager <= 2.5.0 - Unauthenticated Improper Output Neutralization for Logs via log_js_errors AJAX Action

Debug Log Manager – Conveniently Monitor and Inspect Errors · CWE-117 · CWE-117
AffectedDebug Log Manager – Conveniently Monitor and Inspect Errors
FixNo fix listed yet.
PublishedJun 6, 04:28 · Wordfence
ScoredJun 6 · 5.3 · Wordfence
Exploit code publicNone known · checked 21:18 UTC
ExploitedNone known · CISA KEV checked 22:04 UTC

What we know

No known exploitation. CISA KEV, checked 22:04 UTC.
No public exploit code known. Exploit-DB, Metasploit, Nuclei, checked 21:18 UTC.
An attacker only needs network access to the target. No login needed. CVSS: network, no privileges.

Description

The Debug Log Manager – Conveniently Monitor and Inspect Errors plugin for WordPress is vulnerable to Improper Output Neutralization for Logs in all versions up to, and including, 2.5.0. This is due to the `log_js_errors()` AJAX handler being registered for unauthenticated users via `wp_ajax_nopriv_log_js_errors` and gated only by a nonce that is publicly disclosed in every front-end page's HTML through `wp_localize_script()` whenever JavaScript error logging is enabled, providing no real authorization barrier. This makes it possible for unauthenticated attackers to inject arbitrary forged entries into the site's WordPress debug log by supplying attacker-controlled values for the `message`, `script`, `lineNo`, `columnNo`, and `pageUrl` fields — enabling spoofing of error and incident records, obscuring malicious activity within fabricated log noise, and misleading administrators who rely on the log for triage. This vulnerability is only exploitable when the plugin's JavaScript error logging feature is enabled, as the requisite nonce is only published into the page HTML under that condition.

From Wordfence

Affected and fixed versions

ProductAffectedFixed inDebug Log Manager – Conveniently Monitor and Inspect Errorsup to 2.5.0–

Exploit code

Exploit-DBnone knownMetasploitnone knownNucleinone known

References

www.wordfence.com/threat-intel/vulnerabilities/id/25abca87-1be2-427e-ab01-377d52917052?source=cve · wordfence.complugins.trac.wordpress.org/browser/debug-log-manager/tags/2.4.3/classes/class-debug-log.php#L1961 · plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/debug-log-manager/tags/2.4.3/classes/class-debug-log.php#L1947 · plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/debug-log-manager/tags/2.4.3/bootstrap.php#L123 · plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/debug-log-manager/tags/2.4.3/bootstrap.php#L556 · plugins.trac.wordpress.orgplugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3543321%40debug-log-manager&new=3543321%40debug-log-manager&sfp_email=&sfph_mail= · plugins.trac.wordpress.org

Other CVEs in Debug Log Manager – Conveniently Monitor and Inspect Errors

All 3 →
7.2Debug Log Manager <= 2.5.2 - Unauthenticated Stored Cross-Site Scripting via 'log_js_errors' AJAX Endpoint · CVE-2026-120114Oct 317.2Debug Log Manager <= 2.3.4 - Unauthenticated Stored Cross-Site Scripting · CVE-2025-3809Apr 19, 20254.3Debug Log Manager <= 2.2.0 - Cross-Site Request Forgery · CVE-2023-5772Nov 30, 2023