CVE-2026-40770
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 · uneditedUnauthenticated Cross Site Scripting (XSS) in Coupon Affiliates <= 7.5.3 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 confidenceUnauthenticated Cross-Site Scripting (XSS) vulnerability in the Coupon Affiliates WordPress plugin affecting versions 7.5.3 and below. An attacker can inject malicious JavaScript code through unsanitized user input without requiring authentication, potentially leading to 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 checksWork through these to decide whether this CVE applies to you.
-
Check Coupon Affiliates plugin versionGo to WordPress admin dashboard > Plugins > Installed Plugins > Coupon Affiliates. Locate the version number displayed under the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/coupon-affiliates/coupon-affiliates.php for the 'Version' tag.Affected if The displayed version is 7.5.3 or any version number lower than 7.5.3 (e.g., 7.5.2, 7.5.1, 7.5.0, etc.).
-
Verify affiliate tracking functionality is activeNavigate to the plugin settings page in WordPress admin (usually under WooCommerce > Coupon Affiliates or a dedicated Coupon Affiliates menu). Check if affiliate tracking, referral tracking, or any affiliate parameter handling is enabled.Affected if Affiliate tracking features are enabled and the site uses affiliate parameters (such as ref, affiliate, or similar query parameters) in URLs.
-
Inspect affiliate tracking parameters for input handlingExamine the plugin source code in wp-content/plugins/coupon-affiliates/ for files handling affiliate or referral parameters. Look for $_GET or $_REQUEST usage capturing parameters like ref, aff, affiliate_id, or cid without sanitization functions such as sanitize_text_field, esc_html, or esc_attr.Affected if The code reads user-supplied input from URL parameters (e.g., ?ref= attacker input) and outputs it without applying WordPress sanitization or output encoding functions.
-
Test for XSS in affiliate parametersUsing a browser or curl, request a page on the site with a crafted affiliate parameter such as ?ref=<script>alert(1)</script> or ?affiliate_id=<img src=x onerror=alert(1)>. Observe if the unsanitized payload is reflected in the page output.Affected if The parameter value is reflected verbatim in the HTML response without encoding (e.g., <script> tags execute or are visible in the page source).
The site is affected if the Coupon Affiliates plugin version is 7.5.3 or below AND affiliate tracking parameters are in use with unsanitized user input being reflected in page output.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Coupon Affiliates plugin to the latest version. If an update is unavailable, locate and sanitize all user-supplied input fields (likely in affiliate tracking parameters) using appropriate output encoding or WordPress sanitization functions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-40770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40770 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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