Debug Log Manager – Conveniently Monitor and Inspect Errors
debug-log-manager · plugin
Known security vulnerabilities for Debug Log Manager – Conveniently Monitor and Inspect Errors. Find out in seconds which version runs on your site with WP Lens.
8 known vulnerabilities
6 exploitable without logging in · latest Jun 6, 2026
Listed on wordpress.org · latest 2.5.2 · last updated Jun 26, 2026 · 10K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2024-35669login required≤ 2.3.1
WordPress Debug Log Manager plugin <= 2.3.1 - Broken Access Control vulnerability
- High 7.5
CVE-2023-6136unauthenticated≤ 2.3.0
WordPress Debug Log Manager Plugin <= 2.3.0 is vulnerable to Sensitive Data Exposure
- High 7.2
CVE-2025-3809unauthenticated≤ 2.3.4
Debug Log Manager <= 2.3.4 - Unauthenticated Stored Cross-Site Scripting
- High 7.1
CVE-2025-32613unauthenticated · needs a click≤ 2.3.4
WordPress Debug Log Manager plugin <= 2.3.4 - Cross Site Scripting (XSS) vulnerability
- High 7.1
CVE-2024-32582unauthenticated · needs a click≤ 2.3.1
WordPress Debug Log Manager plugin <= 2.3.1 - Cross Site Scripting (XSS) vulnerability
- Medium 5.3
CVE-2026-9016unauthenticated≤ 2.5.0
Debug Log Manager <= 2.5.0 - Unauthenticated Improper Output Neutralization for Logs via log_js_errors AJAX Action
- Medium 4.3
CVE-2023-5772unauthenticated · needs a click≤ 2.2.1
Debug Log Manager <= 2.2.0 - Cross-Site Request Forgery
- Medium 4.3
CVE-2024-33915login required≤ 2.3.1
WordPress Debug Log Manager plugin <= 2.3.1 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).