Missing AuthorizationWeakness · CWE-862

CVE-2025-14070

HIGH · 7.5 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The Reviewify plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'send_test_email' AJAX action in all versions up to, and including, 1.0.7. This makes it possible for authenticated attackers, with Contributor-level access and above, to create arbitrary WooCommerce discount coupons, potentially causing financial loss to the store.

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 Reviewify WordPress plugin is vulnerable to Broken Access Control due to a missing capability check on the 'send_test_email' AJAX action in versions up to 1.0.7. This allows any authenticated user with Contributor-level access or higher to bypass authorization and create arbitrary WooCommerce discount coupons, potentially causing direct financial loss to the store.

MitigationUpdate the Reviewify plugin to version 1.0.8 or later which includes proper capability validation. Until patched, consider disabling new user registration and monitor for unauthorized coupon creation.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify the installed Reviewify plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Reviewify. The version number is displayed beneath the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/reviewify/reviewify.php for the 'Version' tag.
    Affected if The installed version is 1.0.7 or lower (any version up to and including 1.0.7).
  2. Confirm WooCommerce is active
    In WordPress admin, verify WooCommerce status under Plugins > Must-Use Plugins or check for the WooCommerce menu item in the admin sidebar. The vulnerability impact (coupon creation) requires WooCommerce to be present.
    Affected if WooCommerce is installed and active in the WordPress environment.
  3. Check for existing user accounts with Contributor role or higher
    Navigate to Users > All Users in WordPress admin. Review the role column for each account. Alternatively, query the wp_usermeta table filtering for meta_key = 'wp_capabilities' and meta_value containing 'contributor', 'author', 'editor', or 'administrator'.
    Affected if Any user account exists with Contributor, Author, Editor, or Administrator role (authenticated users at Contributor level and above can exploit this flaw).
  4. Verify the send_test_email AJAX action is accessible
    Inspect the plugin AJAX handler registration in reviewify.php or related files. Look for wp_ajax_send_test_email and wp_ajax_nopriv_send_test_email hooks. Check if capability checks (like 'manage_options' or 'edit_products') are absent before the coupon creation logic.
    Affected if The AJAX action 'send_test_email' is registered without a proper capability check (no current_user_can() validation before coupon generation).
  5. Audit recently created WooCommerce coupons for unauthorized creation
    In WordPress admin, go to Marketing > Coupons (WooCommerce). Review the 'Created' column for coupons created by unexpected users or at unusual times. Cross-reference coupon creators against legitimate administrators.
    Affected if Coupons exist in WooCommerce that were created by users without administrative privileges, or creation timestamps correlate with periods when non-admin users had access.

Your environment is affected if the Reviewify plugin version is 1.0.7 or lower AND WooCommerce is active AND at least one user with Contributor-level access exists, allowing unauthorized coupon creation.

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

Update the Reviewify plugin to version 1.0.8 or later which includes proper capability validation. Until patched, consider disabling new user registration and monitor for unauthorized coupon creation.

Recommended fix Moderate confidence

Reviewify version 1.0.8 or latest stable release

  1. Backup your WordPress site and database before making any changes
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the Reviewify plugin
  5. Deactivate and delete the current version of Reviewify
  6. Install version 1.0.8 or the latest available version of the Reviewify plugin
  7. Activate the new version
  8. Verify the plugin is functioning correctly
Caveat Minimal risk - this is a security patch upgrade; review plugin settings after upgrade

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

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-2025-14070 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14070 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