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

CVE-2026-4080

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Easy Cart plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'add_to_cart' shortcode in all versions up to and including 1.8. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. Specifically, the ectp_add_to_cart() function uses sanitize_text_field() on shortcode attributes like 'itemid', 'product_name', 'product_desc', 'product_qty', and 'price' before inserting them into double-quoted HTML attributes. While sanitize_text_field() strips HTML tags, it does not escape double quote characters, allowing an attacker to break out of the HTML attribute context and inject arbitrary event handlers. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The Easy Cart WordPress plugin (versions up to 1.8) has a Stored XSS vulnerability in the ectp_add_to_cart() function. While sanitize_text_field() is used on shortcode attributes (itemid, product_name, product_desc, product_qty, price), it only strips HTML tags without escaping double quotes, allowing attribute injection. Authenticated Contributors+ can inject malicious event handlers via crafted shortcode attributes.

MitigationReplace sanitize_text_field() with proper output escaping functions (esc_attr()) for all shortcode attributes before inserting them into HTML double-quoted attributes, and validate that the fix properly handles all injection attempts.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Easy Cart plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Easy Cart' appears in the installed plugins list, or inspect the filesystem at wp-content/plugins/ for an easy-cart or similar directory
    Affected if The Easy Cart plugin is present in the WordPress installation
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins and look for the Easy Cart plugin version number displayed under the plugin name, or check the plugin header in the main PHP file for 'Version:' tag
    Affected if The version number is 1.8 or lower, or no version number is displayed (indicating an old unversioned release)
  3. Locate usage of add_to_cart shortcode
    Search the WordPress database (wp_posts table) for content containing the shortcode [add_to_cart] or [ectp_add_to_cart], or use a plugin to export and search post content for these shortcode strings
    Affected if The add_to_cart/ectp_add_to_cart shortcode is present in any published post, page, or custom post type
  4. Inspect shortcode attribute values for unescaped quotes
    Examine the shortcode usage found in step 3 and check if any attributes (itemid, product_name, product_desc, product_qty, price) contain double quote characters that could break out of HTML attribute context when the shortcode renders
    Affected if Any add_to_cart shortcode contains attributes with unescaped double quotes, or the plugin is actively processing these shortcodes on the site front-end

A user is affected if the Easy Cart plugin version is 1.8 or lower and the add_to_cart shortcode with vulnerable attributes is in use on the site, allowing Contributor-level users to inject XSS via unsanitized shortcode parameters.

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

Replace sanitize_text_field() with proper output escaping functions (esc_attr()) for all shortcode attributes before inserting them into HTML double-quoted attributes, and validate that the fix properly handles all injection attempts.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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