Skip to main content

Software intelligence

Wp Debugging vulnerabilities

3 tracked advisories · slug wp-debugging

Important: Wp Debugging appearing in this catalog does not mean your website is affected. Exposure depends on your installed version. How SiteRespond intelligence works

Tracked advisories

3

Latest advisory

1 July 2026

CISA KEV matches

0

In this WordPress feed

WordPress slug

wp-debugging

Plugin

What this means for Wp Debugging

This catalog lists 3 known advisories affecting Wp Debugging. The most recent was published on 1 July 2026. If you use this software, compare your installed version against the affected ranges on each advisory and update to a fixed release outside those ranges. SiteRespond Defence checks your actual installed version when the plugin is connected — listing here does not by itself mean your site is vulnerable.

Latest issues

  • WP Debugging <= 2.12.2 - Unauthenticated Stored Cross-Site Scripting

    May allow attackers to run scripts in visitors' browsers or hijack admin sessions.

    Published 1 July 2026

  • WP Debugging <= 2.11.7 - Cross-Site Request Forgery

    May trick authenticated users into performing unintended actions.

    Published 24 January 2022

  • WP Debugging <= 2.10.2 - Unauthenticated Plugin Settings Update

    This advisory describes a other issue in the affected software. Review the source advisory and your installed version to assess exposure.

    Published 27 September 2021

Vulnerability types

  • Cross-site scripting1
  • CSRF1

Authentication (inferred from titles)

  • Unauthenticated2
  • Authenticated0
  • Unspecified1

Advisory history

Known Wp Debugging advisories published by month.

All advisories

Check whether your installed version is affected

SiteRespond Defence matches your installed Wp Debugging version against this catalog when the Defence plugin is connected to your WordPress site.