dbcve.org
CWE-497Weakness · CWE-497

CVE-2026-57633

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-26
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
Unauthenticated Sensitive Data Exposure in WCBoost &#8211; Products Compare <= 1.1.0 versions.

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

This vulnerability in the WCBoost Products Compare WordPress plugin (versions <= 1.1.0) allows unauthenticated attackers to access sensitive data without any authentication. The issue likely stems from missing capability checks or improper access controls on certain plugin functions or AJAX endpoints that expose product comparison data, customer information, or other sensitive WooCommerce data.

MitigationUpdate WCBoost – Products Compare plugin to version 1.1.1 or later if available; otherwise, disable the plugin until a patch is released. Review server access logs for unauthorized access attempts to plugin endpoints.

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. Identify if WCBoost Products Compare plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WCBoost - Products Compare' or check the plugin files in wp-content/plugins/ for a folder containing 'wcboost-products-compare'
    Affected if The plugin is installed and version is 1.1.0 or lower
  2. Determine installed plugin version number
    In WordPress admin Plugins list, click on the plugin to view details, or open the main plugin PHP file (e.g., wcboost-products-compare.php) and look for the 'Version:' header in the plugin comments
    Affected if Version displayed is 1.1.0 or below, or no version number is visible (indicating an old unversioned release)
  3. Identify plugin AJAX endpoints accessible without authentication
    Search plugin PHP files for 'add_action' calls registering AJAX actions (wp_ajax_ and wp_ajax_nopriv_ prefixes), particularly those handling product comparison data or user data. Common paths: wp-content/plugins/wcboost-products-compare/includes/
    Affected if Endpoints registered with 'wp_ajax_nopriv_' allow unauthenticated access to sensitive functions
  4. Test for unauthenticated access to comparison data
    Use a browser or curl to visit common plugin endpoints such as /wp-admin/admin-ajax.php?action=... (replacing ... with plugin action names found in the code), or any direct PHP files in the plugin folder that may handle comparison requests without requiring login
    Affected if Requests return product comparison data, customer information, or WooCommerce data without being logged in (HTTP 200 with data instead of redirect to login or 403 error)
  5. Review server access logs for plugin endpoint activity
    Examine web server access logs (Apache error.log, Nginx access.log, or WordPress debug.log) for requests to admin-ajax.php with plugin-related actions, or direct access to plugin PHP files, noting any from unauthenticated IP addresses
    Affected if Logs show numerous requests to plugin AJAX endpoints from unauthenticated sources, especially if returning successful (200) status codes

A user is affected if the WCBoost Products Compare plugin version is 1.1.0 or lower and the plugin endpoints are accessible without authentication, exposing sensitive data to unauthenticated visitors.

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 WCBoost – Products Compare plugin to version 1.1.1 or later if available; otherwise, disable the plugin until a patch is released. Review server access logs for unauthorized access attempts to plugin endpoints.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

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