CVE-2025-66154
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 · uneditedMissing Authorization vulnerability in merkulove Couponer for Elementor couponer-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Couponer for Elementor: from n/a through <= 1.1.7.
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 confidenceThe Couponer for Elementor plugin versions up to 1.1.7 have a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This broken access control flaw permits users to access functionality beyond their privilege level, likely due to missing capability checks on sensitive AJAX actions or admin pages.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 Couponer for Elementor is installedCheck your WordPress installation for the Couponer for Elementor plugin in wp-content/plugins/ directory, or navigate to Plugins > Installed Plugins in the WordPress admin dashboard and search for 'Couponer for Elementor'.Affected if The plugin is installed and active in WordPress.
-
Determine installed plugin versionOpen the main plugin file (couponer-elementor.php or similar) in the plugins directory and locate the version in the plugin header comment, or check the version displayed on the Plugins admin page.Affected if The installed version is 1.1.7 or any version number lower than 1.1.7.
-
Identify exposed AJAX actionsExamine the plugin PHP files for wp_ajax_ and wp_ajax_nopriv_ hooks. Look for registered AJAX action names using add_action('wp_ajax_...') calls. Common patterns include actions like 'couponer_save_coupon', 'couponer_delete_coupon', or similar coupon management operations.Affected if AJAX actions related to coupon creation, modification, or deletion are registered without capability checks (no current_user_can() verification before processing).
-
Test AJAX endpoint accessibilitySend a direct HTTP POST request to /wp-admin/admin-ajax.php with a suspected AJAX action (action=couponer_*) while logged in as a low-privilege user (e.g., Subscriber) or logged out. Check if the server returns a successful response instead of a 403 or capability error.Affected if The AJAX endpoint responds successfully and performs coupon operations without verifying the user's capability (returns 200 OK with coupon data or performs the action instead of returning a permission denied error).
You are affected if the Couponer for Elementor plugin version 1.1.7 or lower is installed and any AJAX coupon management actions lack current_user_can() capability verification.
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 dataUpdate to the latest version of Couponer for Elementor if available; otherwise, implement proper WordPress capability checks (current_user_can()) on all admin and AJAX functions and restrict access to sensitive coupon management endpoints.
- 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-66154 — 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-66154 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