dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-62884

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in Elliot Sowersby / RelyWP Coupon Affiliates woo-coupon-usage allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Coupon Affiliates: from n/a through <= 7.2.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 confidence

Missing Authorization vulnerability in the Coupon Affiliates WordPress plugin (woo-coupon-usage feature) allows users to access functionality not properly constrained by Access Control Lists (ACLs). The plugin fails to enforce proper capability checks on certain endpoints or functions, potentially allowing authenticated users to perform actions or access data that should be restricted to administrators or higher-privileged users.

MitigationUpgrade to version 7.2.1 or later which contains the authorization fix. If unable to upgrade immediately, audit all plugin endpoints and add proper current_user_can() capability checks and nonce validation to all woo-coupon-usage related functions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm Coupon Affiliates plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Coupon Affiliates' or 'WooCommerce Coupon Affiliates' plugin, or check wp-content/plugins directory for a folder containing 'coupon' or 'woo-coupon-usage'
    Affected if The plugin is installed and active in the WordPress environment
  2. Identify installed plugin version
    In WordPress admin > Plugins, click on the plugin to view its version details, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The version is below 7.2.1 (the fixed version)
  3. Verify the woo-coupon-usage feature is active
    Check WordPress admin menus for any 'Coupon Affiliates' or 'Coupons > Usage' menu items, or look for the woo-coupon-usage shortcode or widget being used on the site
    Affected if The woo-coupon-usage feature is enabled or in use on the site
  4. Check user role capabilities for affected endpoints
    Using a user account with subscriber-level or shop_manager role, attempt to access the plugin admin pages or check if the plugin exposes any public-facing endpoints under /wp-json/ or admin-ajax.php related to coupon usage tracking
    Affected if Lower-privileged users can access admin functionality or sensitive coupon data that should be restricted to administrators

You are affected if the Coupon Affiliates plugin (woo-coupon-usage feature) is installed with a version below 7.2.1 and allows non-administrator users to access restricted plugin functionality.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 7.2.1 or later which contains the authorization fix. If unable to upgrade immediately, audit all plugin endpoints and add proper current_user_can() capability checks and nonce validation to all woo-coupon-usage related functions.

Recommended fix Moderate confidence

Latest version of Coupon Affiliates (plugin version > 7.2.0)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Coupon Affiliates' (woo-coupon-usage) plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. 6. After updating, verify the plugin is functioning correctly on the site

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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