Skip to main content
VulnerabilityPublished

CVE-2026-9016: Debug Log Manager (WordPress plugin) · Log Injection

Affects Debug Log Manager (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
qriousladDebug Log Manager – Conveniently Monitor and Inspect ErrorsAffected
  • <=2.5.0
Fixed in–

AI-suggested

Until a fix is available, administrators should consider disabling the JavaScript error logging feature of the Debug Log Manager plugin to prevent the nonce from being exposed and block unauthenticated log injection. Monitoring for plugin updates or official patches is recommended.

Description

The Debug Log Manager plugin for WordPress up to version 2.5.0 is vulnerable to improper output neutralization for logs. This vulnerability allows unauthenticated attackers to inject forged entries into the WordPress debug log when the plugin's JavaScript error logging feature is enabled. The issue arises because the AJAX handler for logging errors is accessible without authentication and protected only by a nonce that is publicly exposed in the page HTML. This can lead to misleading log entries that obscure malicious activity.

References

Community reviews

Loading reviews…