CVE-2025-14070
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 · uneditedThe 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 confidenceThe 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.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Reviewify plugin versionIn 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).
-
Confirm WooCommerce is activeIn 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.
-
Check for existing user accounts with Contributor role or higherNavigate 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).
-
Verify the send_test_email AJAX action is accessibleInspect 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).
-
Audit recently created WooCommerce coupons for unauthorized creationIn 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.
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 · scopedUpdate 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.
Reviewify version 1.0.8 or latest stable release
- Backup your WordPress site and database before making any changes
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Reviewify plugin
- Deactivate and delete the current version of Reviewify
- Install version 1.0.8 or the latest available version of the Reviewify plugin
- Activate the new version
- Verify the plugin is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14070 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