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

CVE-2026-57313

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
Subscriber Cross Site Scripting (XSS) in SureCart <= 4.2.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 · moderate confidence

A stored Cross Site Scripting (XSS) vulnerability in the SureCart WordPress plugin allows authenticated users with subscriber-level privileges to inject malicious JavaScript code through plugin input fields. The injected payload executes when other users view the affected content.

MitigationUpdate SureCart to a version newer than 4.2.2. If immediate updating is not possible, restrict subscriber-level user capabilities or disable the plugin until a patch can be applied.

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. Verify SureCart plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for SureCart in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed SureCart version
    In WordPress admin, go to Plugins > Installed Plugins. Click on SureCart to view the plugin details, or check the plugin file header in wp-content/plugins/surecart/surecart.php for the Version header.
    Affected if The installed version is 4.2.2 or earlier.
  3. Confirm subscriber-level user accounts exist
    In WordPress admin, go to Users and review the list. Look for users with the Subscriber role specifically.
    Affected if There are user accounts with Subscriber role in WordPress.
  4. Verify subscriber role has access to plugin features
    In WordPress admin, go to Users > Roles > Subscriber. Scroll through the capabilities list and check if any SureCart-related capabilities are granted (typically capabilities containing 'surecart' or related to product/checkout management).
    Affected if Subscriber role has any SureCart-specific capabilities enabled.
  5. Inspect plugin-generated pages for stored XSS vectors
    If you have a subscriber account, log in and navigate to any front-end pages where SureCart displays input forms (product pages, checkout, account settings). Use browser developer tools to view the HTML source of form fields and identify input points.
    Affected if Subscriber-level users can access plugin input fields on any front-end or admin page.

If SureCart version 4.2.2 or earlier is installed AND subscriber-level users exist with access to plugin input fields, the environment is affected by this stored 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 SureCart to a version newer than 4.2.2. If immediate updating is not possible, restrict subscriber-level user capabilities or disable the plugin until a patch can be applied.

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-57313 — 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-57313 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