Debug Log Manager at a glance
- 9 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Oct 30, 2026.
- Ranked #1835 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 2.5.3 (released Oct 19, 2026). The most recent security fix shipped in 2.5.3.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Debug Log Manager version
Enter the Debug Log Manager version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Debug Log Manager”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Debug Log Manager”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.5.3). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Debug Log Manager vulnerabilities
Debug Log Manager <= 2.5.2 - Unauthenticated Stored Cross-Site Scripting via 'log_js_errors' AJAX Endpoint
Cross-site scripting (XSS) · CVE-2026-120114
Affected versions: ≤ 2.5.2
Fixed in: 2.5.3
Severity: High 7.2 · Disclosed Oct 30, 2026
Debug Log Manager <= 2.5.0 - Unauthenticated Improper Output Neutralization for Logs via log_js_errors AJAX Action
Other weakness · CVE-2026-9016
Affected versions: ≤ 2.5.0
Fixed in: 2.5.1
Severity: Medium 5.3 · Disclosed Jun 5, 2026
Debug Log Manager <= 2.3.4 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2025-32613
Affected versions: ≤ 2.3.4
Fixed in: 2.3.5
Severity: High 7.2 · Disclosed Apr 17, 2025
Debug Log Manager <= 2.3.1 - Missing Authorization
Missing authorization · CVE-2024-35669
Affected versions: ≤ 2.3.1
Fixed in: 2.3.2
Severity: Medium 5.4 · Disclosed Jun 3, 2024
Debug Log Manager <= 2.3.1 - Missing Authorization via toggle_debugging
Missing authorization · CVE-2024-33915
Affected versions: ≤ 2.3.1
Fixed in: 2.3.2
Severity: Medium 4.3 · Disclosed Apr 29, 2024
Debug Log Manager <= 2.3.1 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-32582
Affected versions: ≤ 2.3.1
Fixed in: 2.3.2
Severity: High 7.2 · Disclosed Apr 16, 2024
Debug Log Manager <= 2.2.2 - Directory Listing to Sensitive Information Disclosure
Information disclosure · CVE-2023-6383
Affected versions: ≤ 2.2.2
Fixed in: 2.3.0
Severity: Medium 5.3 · Disclosed Dec 13, 2023
Debug Log Manager <= 2.2.0 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2023-5772
Affected versions: ≤ 2.2.1
Fixed in: 2.2.2
Severity: Medium 4.3 · Disclosed Nov 29, 2023
Debug Log Manager <= 2.2.1 - Missing Authorization
Missing authorization · CVE-2023-6136
Affected versions: ≤ 2.2.1
Fixed in: 2.2.2
Severity: Medium 4.3 · Disclosed Nov 23, 2023
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Debug Log Manager <= 2.5.2 - Unauthenticated Stored Cross-Site Scripting via 'log_js_errors' AJAX EndpointCross-site scripting (XSS) · CVE-2026-120114 | ≤ 2.5.2 | 2.5.3 | High 7.2 | Oct 30, 2026 |
| Debug Log Manager <= 2.5.0 - Unauthenticated Improper Output Neutralization for Logs via log_js_errors AJAX ActionOther weakness · CVE-2026-9016 | ≤ 2.5.0 | 2.5.1 | Medium 5.3 | Jun 5, 2026 |
| Debug Log Manager <= 2.3.4 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2025-32613 | ≤ 2.3.4 | 2.3.5 | High 7.2 | Apr 17, 2025 |
| Debug Log Manager <= 2.3.1 - Missing AuthorizationMissing authorization · CVE-2024-35669 | ≤ 2.3.1 | 2.3.2 | Medium 5.4 | Jun 3, 2024 |
| Debug Log Manager <= 2.3.1 - Missing Authorization via toggle_debuggingMissing authorization · CVE-2024-33915 | ≤ 2.3.1 | 2.3.2 | Medium 4.3 | Apr 29, 2024 |
| Debug Log Manager <= 2.3.1 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-32582 | ≤ 2.3.1 | 2.3.2 | High 7.2 | Apr 16, 2024 |
| Debug Log Manager <= 2.2.2 - Directory Listing to Sensitive Information DisclosureInformation disclosure · CVE-2023-6383 | ≤ 2.2.2 | 2.3.0 | Medium 5.3 | Dec 13, 2023 |
| Debug Log Manager <= 2.2.0 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2023-5772 | ≤ 2.2.1 | 2.2.2 | Medium 4.3 | Nov 29, 2023 |
| Debug Log Manager <= 2.2.1 - Missing AuthorizationMissing authorization · CVE-2023-6136 | ≤ 2.2.1 | 2.2.2 | Medium 4.3 | Nov 23, 2023 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 30, 2026.
Most common weaknesses in Debug Log Manager
Cross-site scripting (XSS)
3 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Missing authorization
3 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Information disclosure
1 issue
Data that should stay private, such as user details or configuration values, can be read from outside.
Frequently asked questions
Is Debug Log Manager safe to use?
Debug Log Manager is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.5.3) and turn on automatic updates.
How do I find which version of Debug Log Manager my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesDebug Log Manager on WordPress.org