CVE-2026-9016 MEDIUM

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

Vendor Qriouslad
Product Debug Log Manager – Conveniently Monitor and Inspect Errors
Weakness CWE-117
Published June 6, 2026
Last update June 6, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Debug Log Manager versions 2.5.0 and earlier contain an improper input validation flaw that allows attackers to inject malicious data into log files. An attacker with network access can craft requests that corrupt or manipulate debug log entries without authentication. This could lead to log tampering, making it difficult to detect other attacks or troubleshoot legitimate issues.

What an attacker can do

03Attacker Capabilities

Inject malicious content into debug log files to corrupt logs or hide attack traces.

Potential impact on your site

04Site Impact

Debug logs become unreliable for troubleshooting; attackers can cover their tracks by poisoning log entries.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

June 6, 2026 CVE published
June 6, 2026 Record updated