dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-12584

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-27
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
The Quick View for WooCommerce plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.2.17 via the 'wqv_popup_content' AJAX endpoint due to insufficient restrictions on which products can be included. This makes it possible for unauthenticated attackers to extract data from private products that they should not have access to.

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 Quick View for WooCommerce plugin for WordPress has an information exposure vulnerability in all versions up to 2.2.17. The 'wqv_popup_content' AJAX endpoint lacks proper authorization checks, allowing unauthenticated attackers to extract sensitive data from private products that should be restricted.

MitigationUpdate the plugin to version 2.2.18 or later which contains proper authorization controls. Until then, consider disabling the quick view functionality or restricting access to the AJAX endpoint via server-side configuration.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
    Locate the Quick View for WooCommerce plugin files in the WordPress wp-content/plugins directory. Check the main plugin file (typically quick-view-for-woocommerce.php or similar) for the plugin header which contains the version number.
    Affected if The plugin is installed and the version is 2.2.17 or lower (or the version cannot be determined but the plugin is present).
  2. Confirm the installed version
    Read the plugin version from the plugin header comment in the main PHP file, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name LIKE '%quick_view_for_woocommerce%version%'.
    Affected if The version number returned is 2.2.17 or lower, or the version cannot be reliably determined.
  3. Test AJAX endpoint accessibility
    Send a crafted POST request to your site's /wp-admin/admin-ajax.php endpoint with action=wqv_popup_content and a product ID parameter (such as product_id=1). Use a tool like curl: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=wqv_popup_content&product_id=1'.
    Affected if The endpoint returns HTTP 200 and exposes product content (including private product details) without requiring authentication or authorization verification.
  4. Check for private products that could be exposed
    Query the WooCommerce products database: SELECT ID, post_title, post_status FROM wp_posts WHERE post_type='product' AND post_status='private'. Alternatively, use WooCommerce REST API or admin panel to list products with visibility set to private.
    Affected if There are products with private status in the WooCommerce store, and these could be retrieved via the vulnerable AJAX endpoint.

You are affected if the Quick View for WooCommerce plugin is installed with version 2.2.17 or lower and the wqv_popup_content AJAX endpoint returns product data (including private products) without requiring authentication.

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

Update the plugin to version 2.2.18 or later which contains proper authorization controls. Until then, consider disabling the quick view functionality or restricting access to the AJAX endpoint via server-side configuration.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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