CVE-2026-9016
MediumCVSS 5.3Summary
The Debug Log Manager plugin for WordPress is vulnerable to improper output neutralization for logs in all versions up to 2.5.0. The issue arises from the registration of the `log_js_errors()` AJAX handler for unauthenticated users, allowing for the injection of forged entries into the debug log.
Risk Assessment
Attackers can inject false data into the logs, leading to the spoofing of error and incident records. This can mislead administrators who rely on these logs for triage.
Recommendation
It is recommended to disable the JavaScript error logging feature of the plugin or implement additional authorization mechanisms to secure access to the AJAX handler.
Original NVD description (English source)
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.