Plugins · wp-debugging · data as of 2026-11-04
Is WP Debugging safe? Known vulnerabilities and latest version
- Latest version
- 2.12.6
- Last updated
- 2026-08-13
- Active installs
- 10,000+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 5.6+
A support/troubleshooting plugin for WordPress. — by Andy Fragen
What to do
- Update to the latest version (2.12.6). Anything older than 2.12.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get wp-debugging --field=version shows what you run; wp plugin update wp-debugging updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 7.1 CVE-2026-57350 · published 2026-07-02
Cross-site scripting (XSS) in WP Debugging (2.12.2 and older)
- Affected
- 2.12.2 and older
- Fixed in
- 2.12.3
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Cross Site Scripting (XSS) in WP Debugging <= 2.12.2 versions.
medium 6.5 CVE-2021-24779 · published 2021-10-25
Cross-site request forgery (CSRF) in WP Debugging (older than 2.11.0)
- Affected
- older than 2.11.0
- Fixed in
- 2.11.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The WP Debugging WordPress plugin before 2.11.0 has its update_settings() function hooked to admin_init and is missing any authorisation and CSRF checks, as a result, the settings can be updated by unauthenticated users.
Recent activity
- 2026-08-13 — latest release on wordpress.org (2.12.6).
- 2026-07-02 — Cross-site scripting (XSS) disclosed (CVE-2026-57350), fixed in 2.12.3.
- 2021-10-25 — Cross-site request forgery (CSRF) disclosed (CVE-2021-24779), fixed in 2.11.0.
Get an email when WP Debugging has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for WP Debugging (wp-debugging) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by Andy Fragen (2 tracked)
Types found in this plugin: Cross-site scripting (XSS) (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wp-debugging (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/wp-debugging"><img src="https://laskyr.com/plugins/wp-debugging/badge.svg" alt="WP Debugging vulnerability status"></a>