WordPress plugin
WP Debugging security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 3 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High2
- Medium1
- Low0
All WP Debugging vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.2 | Unauthenticated Stored Cross-Site Scripting ≤2.12.2Update to 2.12.3 | CVE-2026-57350 | |
| High8.8 | Cross-Site Request Forgery ≤2.11.7Update to 2.11.8 | — | |
| Medium6.5 | Unauthenticated Plugin Settings Update ≤2.10.2Update to 2.11.0 | CVE-2021-24779 |
- High7.2Unauthenticated Stored Cross-Site Scripting
≤2.12.2Update to 2.12.3
- High8.8Cross-Site Request Forgery
≤2.11.7Update to 2.11.8
- Medium6.5Unauthenticated Plugin Settings Update
≤2.10.2Update to 2.11.0
WP Debugging: common questions
Does WP Debugging have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in WP Debugging: 2 high, 1 medium. None are known to affect version null.
How do I check which version of WP Debugging I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent WP Debugging vulnerability?
CVE-2026-57350, published Jul 1, 2026: WP Debugging <= 2.12.2 - Unauthenticated Stored Cross-Site Scripting. Severity: High (CVSS 7.2).
Is any WP Debugging vulnerability listed in CISA KEV?
No. None of the known WP Debugging vulnerabilities is currently listed in the CISA KEV catalog.