CVE-2026-45438
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 WebToffee Smart Coupons for WooCommerce allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Smart Coupons for WooCommerce: from n/a before 2.3.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 confidenceThis is a missing authorization (broken access control) vulnerability in the WebToffee Smart Coupons for WooCommerce plugin. The vulnerability allows unauthenticated or unauthorized users to exploit incorrectly configured access control security levels, potentially accessing administrative coupon management functions they should not have permission to use.
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.
-
Locate the Smart Coupons plugin installationCheck the WordPress plugins directory at wp-content/plugins/ for a folder named 'smart-coupons-for-woocommerce' or similar WebToffee coupon plugin folder. If using a managed host, access via FTP or file manager.Affected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed plugin versionOpen the main plugin PHP file (usually the first PHP file in the plugin folder) and locate the 'Version' header in the plugin comment block at the top. Alternatively, log into the WordPress admin dashboard, go to Plugins > Installed Plugins, and find the Smart Coupons entry to see its current version number.Affected if The version number displayed is lower than 2.3.0 (for example: 2.2.9, 2.2.8, 2.0.x, etc.)
-
Verify the plugin is active on the siteIn the WordPress admin under Plugins > Installed Plugins, confirm the Smart Coupons for WooCommerce plugin shows as 'Active'. A plugin must be active for the authorization bypass to be exploitable.Affected if The plugin is installed AND active AND the version is below 2.3.0
-
Check for unauthorized coupon creation capabilityInspect the roles and capabilities on the site using a role editor plugin or by examining user accounts. Look for any user roles other than Administrator that have access to coupon creation or coupon management screens, or check if lower-privileged users (like Shop Managers or Subscribers) can access the Smart Coupons admin interface at wc-admin&page=smart_coupons.Affected if Non-administrator users (such as Shop Managers, Editors, or lower roles) can access the coupon management functionality when they should not be able to
The site is affected if the WebToffee Smart Coupons for WooCommerce plugin is installed, active, and running a version earlier than 2.3.0, allowing unauthorized users to access coupon management functions they should not have permission to use.
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 Smart Coupons for WooCommerce to version 2.3.0 or later which contains the authorization fix. If immediate updating is not possible, audit user roles and permissions for the plugin and consider restricting access to affected endpoints at the web server level.
Upgrade Smart Coupons for WooCommerce to version 2.3.0 or later
- 1. Backup your WordPress database and files before making any changes.
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
- 3. Locate 'Smart Coupons for WooCommerce' by WebToffee.
- 4. If an update is available, click 'Update Now' to upgrade to version 2.3.0 or later.
- 5. Alternatively, download version 2.3.0 or the latest version from the official WordPress repository or WebToffee website.
- 6. Deactivate and delete the current plugin, then upload and install the updated version.
- 7. After upgrading, verify that the plugin is functioning correctly by testing coupon creation and redemption.
- 8. Confirm the authorization controls are working as expected.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45438 — 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-2026-45438 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