dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66114

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-21
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 theme funda Show Variations as Single Products Woocommerce woo-show-single-variations-shop-category allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Show Variations as Single Products Woocommerce: from n/a through <= 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 WooCommerce plugin 'Show Variations as Single Products' (woo-show-single-variations-shop-category) allows unauthenticated or unauthorized users to access functionality that should be restricted. The plugin fails to properly enforce access control checks, enabling attackers to exploit incorrectly configured security levels.

MitigationImplement proper authorization checks (capability checks, nonce verification, and role-based access control) on all sensitive endpoints and functions within the plugin. Ensure all actions that require elevated privileges validate user capabilities before execution.

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. Verify the plugin is installed
    Check if the 'woo-show-single-variations-shop-category' or 'Show Variations as Single Products' plugin exists in the WordPress plugins directory (wp-content/plugins/) or via WP-CLI: wp plugin list --name='woo-show-single-variations'
    Affected if Plugin is installed and active
  2. Identify the installed plugin version
    Check the plugin main file header for the Version field, or use WP-CLI: wp plugin get woo-show-single-variations-shop-category --field=version
    Affected if Version cannot be determined or falls within an affected range (if known)
  3. Inspect plugin endpoints for authorization checks
    Examine the plugin PHP files for action hooks (add_action) and AJAX handlers. Look for functions that handle sensitive operations and verify if they include current_user_can(), nonce verification (check_admin_referer/check_ajax_referer), or capability checks before executing logic
    Affected if Sensitive functions lack capability checks or nonce verification
  4. Test if public-facing functionality accepts unauthorized requests
    If the plugin exposes any front-end URLs, forms, or AJAX endpoints, attempt to access or submit requests without authentication or with a low-privilege user account to verify if actions execute without authorization failures
    Affected if Requests execute successfully without proper authentication or authorization
  5. Check WordPress user role permissions
    Review the plugin code to identify which user roles/capabilities are required for its core functions, then verify if those checks are actually enforced in the relevant callback functions
    Affected if Plugin claims to require specific capabilities but does not enforce them in code

A user is affected if the plugin is installed and its sensitive functions execute without verifying user capabilities or validating nonces, allowing unauthorized access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks (capability checks, nonce verification, and role-based access control) on all sensitive endpoints and functions within the plugin. Ensure all actions that require elevated privileges validate user capabilities before execution.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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