dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-52711

HIGH · 7.5 CVSS v3.1 Published 2026-06-16
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

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 Broken Access Control in WooCommerce POS <= 1.8.14 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

Unauthenticated Broken Access Control vulnerability in WooCommerce POS plugin versions 1.8.14 and earlier allows remote attackers to access sensitive functionality or data without proper authentication. The vulnerability involves missing authorization checks on certain endpoints or actions, potentially exposing administrative operations or customer data.

MitigationUpdate WooCommerce POS to the latest patched version (1.8.15 or later). If no patch is available, temporarily disable the plugin or restrict access to the WooCommerce POS endpoints via web server configuration until a fix is released.

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 WooCommerce POS plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WooCommerce POS' in the list of active plugins.
    Affected if The plugin is present and active in the WordPress installation.
  2. Identify installed WooCommerce POS version
    In the WordPress admin, go to Plugins > Installed Plugins and find WooCommerce POS. The version number is displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/woocommerce-pos/woocommerce-pos.php for the 'Version' comment.
    Affected if A version number is found in the plugin files.
  3. Compare version against affected range
    Compare the installed version number to the affected range: versions 1.8.14 and earlier are vulnerable. Any version up to and including 1.8.14 is affected.
    Affected if The installed version is 1.8.14 or earlier (e.g., 1.8.14, 1.8.13, 1.8.12, etc.).
  4. Check for unauthenticated endpoint access
    Attempt to access common WooCommerce POS REST API endpoints without authentication (e.g., /wp-json/wc-pos/v1/ endpoints). Use a tool like curl to send requests to these endpoints without providing authentication credentials.
    Affected if The endpoints respond without requiring authentication, indicating missing authorization checks.

The environment is affected if WooCommerce POS version 1.8.14 or earlier is installed and the vulnerable endpoints are accessible without 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 WooCommerce POS to the latest patched version (1.8.15 or later). If no patch is available, temporarily disable the plugin or restrict access to the WooCommerce POS endpoints via web server configuration until a fix is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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