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

CVE-2026-57711

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-13
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 5 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in PSM Plugins SupportCandy supportcandy allows Stored XSS.This issue affects SupportCandy: from n/a through <= 3.4.8.

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 SupportCandy WordPress plugin (versions through 3.4.8). The vulnerability allows attackers to inject malicious JavaScript code through plugin input fields, which is then stored in the database and executed when other users view the affected content.

MitigationUpdate SupportCandy to the latest version which includes proper input sanitization and output escaping. Until patched, restrict administrative access and sanitize any user-supplied data before storage or display.

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. Confirm SupportCandy plugin is installed
    Log in to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'SupportCandy' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'supportcandy'.
    Affected if SupportCandy plugin is found in the WordPress installation
  2. Check installed SupportCandy version
    In WordPress admin, go to Plugins > Installed Plugins and locate SupportCandy; the version number is displayed below the plugin name. Alternatively, read the 'readme.txt' or 'supportcandy.php' main file in /wp-content/plugins/supportcandy/ to find the 'Version' header.
    Affected if The version number is 3.4.8 or lower (any version through 3.4.8 is affected)
  3. Identify accessible SupportCandy input fields
    Navigate to WP Admin > SupportCandy > Custom Fields. Review which fields are set as 'Agent Only' = No, meaning these fields accept input from end users submitting tickets. Common field types include text, textarea, email, and dropdown fields.
    Affected if Any custom field is configured to accept public/user input (Agent Only = No) - this enables the stored XSS attack vector
  4. Inspect database for suspicious content in ticket data
    Access the WordPress database (via phpMyAdmin or command line). Query the SupportCandy ticket data tables (typically wp_usermeta or custom tables starting with 'wpsc_' prefix) for unescaped HTML/script tags in ticket fields. Example SQL: SELECT * FROM wp_usermeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%onerror=%';
    Affected if Records contain raw HTML tags (like <script>, <img onerror=, or other JavaScript vectors) in ticket custom field data

A WordPress site is affected if SupportCandy plugin version 3.4.8 or lower is installed AND custom fields are exposed to non-admin users, allowing injection of unsanitized content into the database.

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 SupportCandy to the latest version which includes proper input sanitization and output escaping. Until patched, restrict administrative access and sanitize any user-supplied data before storage or display.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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