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

CVE-2026-57629

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 8 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
Contributor Cross Site Scripting (XSS) in StatCounter <= 2.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

A stored Cross Site Scripting (XSS) vulnerability exists in the StatCounter WordPress plugin versions 2.1.1 and below. The flaw allows users with contributor-level permissions to inject malicious scripts through plugin functionality, which then executes when other users view the affected content.

MitigationUpdate the StatCounter plugin to the latest available version. If no patched version exists, consider disabling the plugin until a security update is released.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if StatCounter plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for StatCounter, or check the /wp-content/plugins/ directory for a statcounter folder
    Affected if The StatCounter plugin is present in the WordPress installation
  2. Determine installed StatCounter plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find StatCounter, and view the version number displayed under the plugin name. Alternatively, check the version in the plugin's main PHP file header
    Affected if The version number is 2.1.1 or lower
  3. Check for contributor-level user accounts
    In WordPress admin, go to Users and review the list of users. Note that any user with Contributor role or higher has the permission level needed to exploit this vulnerability
    Affected if There are user accounts with Contributor role or above who have access to the WordPress admin
  4. Inspect plugin output for suspicious scripts
    View the frontend pages where the StatCounter plugin is active (typically pages containing the tracking code). View the page source and look for any unexpected <script> tags, javascript: URLs, or event handlers (onclick, onload, onerror) that may have been injected
    Affected if Unexpected script tags or javascript event handlers appear in the page source where StatCounter content is displayed

You are affected if the StatCounter plugin is installed with version 2.1.1 or below and you have users with Contributor-level or higher access to your WordPress admin.

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 StatCounter plugin to the latest available version. If no patched version exists, consider disabling the plugin until a security update is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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