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

CVE-2026-57672

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 wpDataTables <= 6.5.1.1 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 · moderate confidence

An unauthenticated cross-site scripting (XSS) vulnerability exists in the wpDataTables WordPress plugin versions 6.5.1.1 and below. Attackers can inject malicious scripts through unspecified input vectors without requiring authentication, potentially compromising site visitors or administrators.

MitigationUpdate wpDataTables to the latest version immediately. Since this is an unauthenticated XSS with CVSS 7.1, prioritize patching to prevent potential session hijacking or credential theft.

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. Confirm wpDataTables plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and search for wpDataTables in the list
    Affected if wpDataTables appears in the installed plugins list
  2. Locate the installed version number
    In the plugins list, click on the wpDataTables plugin to expand its details; the version number is displayed in the plugin description area
    Affected if Version displayed is 6.5.1.1 or lower
  3. Verify version via readme.txt (alternative method)
    Access the file /wp-content/plugins/wpdatatables/readme.txt on the server and look for the 'Stable tag' field in the file header
    Affected if Stable tag version listed is 6.5.1.1 or below
  4. Assess vulnerability applicability
    This is an unauthenticated XSS vulnerability - no specific plugin configuration or feature enablement is required for exploitation; any WordPress site running the affected version is potentially vulnerable
    Affected if wpDataTables version is 6.5.1.1 or below

The environment is affected if wpDataTables plugin is installed with a version of 6.5.1.1 or below.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update wpDataTables to the latest version immediately. Since this is an unauthenticated XSS with CVSS 7.1, prioritize patching to prevent potential session hijacking or credential theft.

Recommended fix Moderate confidence

wpDataTables latest version (newer than 6.5.1.1)

  1. 1. Update wpDataTables to the latest available version from the official WordPress plugin repository or vendor
  2. 2. After updating, verify that the plugin version is newer than 6.5.1.1
  3. 3. Test the updated plugin to ensure the XSS vulnerability is remediated
  4. 4. Clear any caching systems if used

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57672 — 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-57672 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