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

> Unauthenticated attackers can inject forged entries into WordPress debug logs via a publicly exposed nonce, obscuring malicious activity and misleading administrators.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2026
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-mqgx-5f5c-w96h

## What is CVE-2026-9016?

CVE-2026-9016 is a medium-severity vulnerability in qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors, published on 6 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2026-9016?


## How do I fix CVE-2026-9016?

No fix has been published for CVE-2026-9016 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9016 being exploited?

There is no known exploitation of CVE-2026-9016 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9016 and fix it if it is affected.

What it is: CVE-2026-9016 is a medium-severity vulnerability in qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors, published on 6 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9016 in the wild and no public exploit code.

Affected product: qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9016/ (Markdown: https://insights.sbomify.com/CVE-2026-9016/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9016
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9016
- OSV: https://osv.dev/vulnerability/CVE-2026-9016

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9016/
Summaries are generated and may contain mistakes; the official description above is the record.