dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57350

HIGH · 7.1 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthenticated Cross Site Scripting (XSS) in WP Debugging <= 2.12.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated Cross Site Scripting (XSS) vulnerability exists in the WP Debugging WordPress plugin versions 2.12.2 and below, allowing attackers to inject malicious scripts into the application without authentication.

MitigationUpdate the WP Debugging plugin to a version newer than 2.12.2 to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the WP Debugging plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-debugging' or 'wordpress-debugging', or query the WordPress database wp_options table for the active_plugins option to see if WP Debugging is listed.
    Affected if The plugin folder exists or the plugin is registered in WordPress.
  2. Determine the installed version
    Open the main plugin file (typically wp-content/plugins/wp-debugging/wp-debugging.php) and locate the 'Version' header in the plugin comment block, or run 'wp plugin list' via WP-CLI if available.
    Affected if The version number displayed is 2.12.2 or lower.
  3. Verify the plugin is active
    Check the WordPress admin dashboard under Plugins > Installed Plugins, or query the wp_options table for the option_name 'active_plugins' to confirm WP Debugging is enabled.
    Affected if The plugin shows as 'Active' or is present in the active_plugins array.
  4. Check if the vulnerable feature is exposed
    Inspect the plugin's admin menu and public-facing functionality to determine if the debugging settings or related endpoints are accessible without authentication, as this is an unauthenticated XSS.
    Affected if Any debugging-related output, settings pages, or AJAX endpoints are accessible to unauthenticated users.

If WP Debugging plugin version 2.12.2 or lower is installed and active with an exposed endpoint, the environment is affected by this unauthenticated XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP Debugging plugin to a version newer than 2.12.2 to remediate this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57350 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data