dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11568

HIGH · 7.5 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

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 Product Configurator for WooCommerce WordPress plugin before 1.7.3 does not perform any authorisation or post-status check before returning WooCommerce product data through a public AJAX action, allowing unauthenticated users to retrieve the data (title, price, weight, stock status, and configurator option pricing/SKUs) of private and draft, non-public products by supplying the product ID. WordPress post-visibility controls are bypassed.

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 Product Configurator for WooCommerce plugin before version 1.7.3 exposes a public AJAX action that returns WooCommerce product data without any authorization checks or validation of post visibility status. Unauthenticated attackers can retrieve sensitive product information (titles, prices, weights, stock status, and configurator pricing/SKUs) including private and draft products by simply supplying a product ID, bypassing WordPress's built-in post-visibility controls.

MitigationUpdate the Product Configurator for WooCommerce plugin to version 1.7.3 or later, which implements proper authorization and post-status validation. Until patched, consider disabling the affected AJAX endpoint or restricting access 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Product Configurator for WooCommerce is installed
    Locate the plugin in WordPress wp-content/plugins directory or check via WordPress admin plugins list
    Affected if The plugin is present in the installation
  2. Check installed plugin version
    Inspect the main plugin file header or view version in WordPress admin plugin list; compare to 1.7.3
    Affected if Version is below 1.7.3 or version cannot be determined (indicating an unpatched old installation)
  3. Confirm AJAX endpoint accessibility
    Identify and test any public AJAX actions exposed by the plugin (typically found in plugin PHP files via wp_ajax or wp_ajax_nopriv hooks); attempt a request without authentication
    Affected if The plugin exposes an AJAX endpoint callable without authentication
  4. Verify unauthorized product data retrieval
    Submit a request to the exposed AJAX endpoint with a product ID (including private or draft products if possible) and observe whether product data is returned without authorization
    Affected if Product information is returned without requiring authentication or validating post visibility status

A user is affected if the Product Configurator for WooCommerce plugin is installed with a version below 1.7.3 and exposes a callable AJAX endpoint that returns product data to unauthenticated users without checking authorization or post visibility status.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Product Configurator for WooCommerce plugin to version 1.7.3 or later, which implements proper authorization and post-status validation. Until patched, consider disabling the affected AJAX endpoint or restricting access via server-side configuration.

Recommended fix High confidence

1.7.3

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Product Configurator for WooCommerce'
  4. Check the current version installed
  5. If the version is below 1.7.3, click 'Update Now' to upgrade to version 1.7.3
  6. After updating, verify the AJAX action is no longer accessible to unauthenticated users by attempting to access the endpoint without authentication
  7. Alternatively, update via WordPress.org repository by searching for 'Product Configurator for WooCommerce' and installing the latest version
Caveat Minor plugin updates typically do not introduce breaking changes; however, test the update in a staging environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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