Reported vulnerability
Debug Log Manager <= 2.5.0 - Unauthenticated Improper Output Neutralization for Logs via log_js_errors AJAX Action
Published 5 Jun 2026
Updated 6 Jun 2026
CVE-2026-9016
Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.
Does this affect my version?
Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.
Wordfence advisory
medium · CVSS 5.3The 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.
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Debug Log Manager – Conveniently Monitor and Inspect Errors
- Software
- plugin · debug-log-manager
- Affected versions
- Start version unspecified, through 2.5.0
- Fix availability
- Fix available
- Fixed versions
- 2.5.1
Recommended action
Update to version 2.5.1, or a newer patched version
Further references (1)
Data sources and licences
Copyright 2012-2026 Defiant Inc.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Read licence termsCopyright 1999-2026 The MITRE Corporation
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Read licence termsSource: Wordfence
Need help fixing this issue?
Get help checking your site, applying an available update and resolving any problems after updating.
Get help with this issueQuestions about this vulnerability
Which versions of Debug Log Manager – Conveniently Monitor and Inspect Errors are affected?
Wordfence lists these affected versions: Start version unspecified, through 2.5.0. Use the version checker above to compare your installed release with this report.
Is a fix available for Debug Log Manager – Conveniently Monitor and Inspect Errors?
Wordfence reports a fix for this issue in Debug Log Manager – Conveniently Monitor and Inspect Errors. It lists these fixed versions: 2.5.1. Back up your website and test the recommended update before applying it to your live site.
Where can I find my installed plugin version?
In WordPress, open Plugins > Installed Plugins and find the version shown beneath the plugin name.
Does an affected version mean my website has been hacked?
An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.
Other reports for the same product
These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.
- Debug Log Manager <= 2.3.4 - Unauthenticated Stored Cross-Site ScriptingUpdated 21 Apr 2025
- Debug Log Manager <= 2.3.4 - Unauthenticated Stored Cross-Site ScriptingUpdated 15 Apr 2026
- Debug Log Manager <= 2.3.1 - Missing AuthorizationUpdated 11 Jun 2024
- Debug Log Manager <= 2.3.1 - Missing Authorization via toggle_debuggingUpdated 7 May 2024
- Debug Log Manager <= 2.3.1 - Unauthenticated Stored Cross-Site ScriptingUpdated 24 Apr 2024