Woocommerce AffiliateWordPress extension · Couponaffiliates
CVE-2023-30475
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Elliot Sowersby, RelyWP WooCommerce Affiliate Plugin – Coupon Affiliates plugin <= 5.4.5 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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the Coupon Affiliates plugin for WooCommerce. The flaw allows an unauthenticated attacker to inject malicious JavaScript code through crafted URLs, which is then reflected back to the victim without proper sanitization or encoding. This can lead to session hijacking, credential theft, or malicious actions performed in the context of the victim's session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Woocommerce AffiliateWordPress extension
<= 5.4.5CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedNavigate to WordPress admin > Plugins and verify 'Couponaffiliates Woocommerce Affiliate' appears in the installed plugins listAffected if The plugin is not listed in the WordPress plugins directory
-
Check installed version numberIn WordPress admin > Plugins, locate 'Couponaffiliates Woocommerce Affiliate' and view the version number displayed beneath the plugin nameAffected if The installed version is 5.4.5 or any version lower (e.g., 5.4.0, 5.3.x, etc.)
-
Inspect URL parameters for reflection pointsIf the plugin is active, review the site's public-facing pages for any URL parameters that might reflect user input (such as query strings in coupon referral links) - examine the HTML source of the rendered page to see if parameter values appear unsanitizedAffected if URL parameter values are reflected in the page output without HTML encoding or sanitization
-
Verify lack of input validationTest the affected parameter (if identified) by crafting a URL with a benign test string like '<script>alert(1)</script>' as a parameter value and observe whether the script tags appear literally in the page sourceAffected if The test string renders as executable HTML/JavaScript rather than being encoded or stripped
You are affected if the Couponaffiliates Woocommerce Affiliate plugin is installed and the version is 5.4.5 or lower, and the vulnerable URL parameter reflection point is accessible on your site.
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 dataUpgrade to a version newer than 5.4.5, or apply vendor-provided patch. Until fixed, users should avoid clicking untrusted links to the affected site.
Fix this in Woocommerce Affiliate
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30475 — 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-2023-30475 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