Live › vulnerability › CVE-2026-120114
The Debug Log Manager plugin for WordPress up to and including 2.5.2 fails to sanitize the message and pageUrl values it stores from JavaScript error reports. An unauthenticated attacker can plant scripts that run in the browser of any user who opens the affected admin log page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 10:34 UTC. All times on this page are UTC.
Sites running Debug Log Manager 2.5.2 or earlier with debug logging and JS error logging turned on are exposed, because the plugin stores attacker-supplied error reports. The attacker needs the publicly emitted nonce, which appears on every frontend page, so no account is required. Sites with the plugin absent, on a later version, or with JS error logging off can skip it.
No product ranges from the sources yet.
wp plugin get debug-log-manager --field=version2.5.2 once the vendor publishes oneEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-120114")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.