CVE-2025-54022
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Elliot Sowersby / RelyWP Coupon Affiliates woo-coupon-usage allows Cross Site Request Forgery.This issue affects Coupon Affiliates: from n/a through <= 6.4.0.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Coupon Affiliates plugin (woo-coupon-usage) allows attackers to trick authenticated users into performing unintended actions on the WordPress site by forcing their browser to send malicious requests.
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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
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.
-
Verify Coupon Affiliates plugin is installedNavigate to WordPress admin > Plugins and look for 'Coupon Affiliates' (woo-coupon-usage) in the list of installed plugins, or check the /wp-content/plugins/ directory for a folder named 'woo-coupon-usage'Affected if the plugin is installed and active
-
Identify installed plugin versionIn WordPress admin > Plugins, click on the plugin details to view the version number, or read the main plugin file (woo-coupon-usage.php) and look for the 'Version' header in the plugin commentsAffected if the version is before the patched release (compare against the vendor's security advisory once available)
-
Check admin forms for missing nonce fieldsExamine the plugin's PHP files in the /wp-content/plugins/woo-coupon-usage/ directory, specifically form handlers and admin pages. Search for $_POST or $_GET submissions that lack wp_verify_nonce or check_admin_referer calls before processingAffected if forms process data without verifying a nonce token, making them vulnerable to CSRF
-
Inspect AJAX actions for missing nonce verificationSearch plugin PHP files for 'add_action' hooks on 'wp_ajax_' and verify each handler calls wp_verify_nonce or check_ajax_referer before executing. Also check 'wp_ajax_nopriv' actions if the plugin allows unauthenticated accessAffected if AJAX endpoints process requests without validating nonce tokens
-
Review frontend or user-facing submission pointsLocate any public-facing forms (coupon submission, affiliate links, etc.) within the plugin and verify they include a nonce field (wp_nonce_field) or that the handler validates a nonce before processingAffected if user-facing forms lack CSRF protection tokens
A user is affected if the Coupon Affiliates plugin is installed, running a version prior to the patched release, and contains forms or AJAX actions that process requests without validating nonce tokens.
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 dataImplement anti-CSRF tokens (nonce verification) on all forms and AJAX actions within the plugin, and update to the patched version once released.
- 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-2025-54022 — 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-2025-54022 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