dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-6072

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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 Oliver POS – A WooCommerce Point of Sale (POS) plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in all versions up to and including 2.4.2.6. The plugin protects its entire /wp-json/pos-bridge/* REST API namespace through the oliver_pos_rest_authentication() permission callback, which uses a loose PHP comparison (==) to compare the attacker-supplied 'OliverAuth' header value against the 'oliver_pos_authorization_token' option. On fresh installations where the admin has not yet completed the connection flow, this option is unset (get_option returns false). Due to PHP's type juggling, the loose comparison '0' == false evaluates to true, allowing an unauthenticated attacker to bypass authentication by sending 'OliverAuth: 0'. This grants full access to all POS API endpoints, enabling attackers to read user data (including administrator details), update user profiles (including email addresses), and delete non-admin users. An admin account email reset can lead to site takeover.

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 Oliver POS WordPress plugin uses a loose PHP comparison (==) to validate the 'OliverAuth' header against the 'oliver_pos_authorization_token' option. On fresh installations where this option is unset, get_option returns false, causing the loose comparison '0' == false to evaluate to true. This allows unauthenticated attackers to bypass authentication by simply sending 'OliverAuth: 0', granting full access to all POS API endpoints including reading/updating user data and deleting users.

MitigationUpdate the plugin to the latest version once available. Ensure the admin completes the connection flow to set the authorization token, which prevents the false comparison trigger.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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. Identify Oliver POS plugin installation
    Check the WordPress plugins directory or use wp plugin list to see if Oliver POS is installed. Note the installed version from the plugin header.
    Affected if Oliver POS plugin is present in the WordPress installation
  2. Check the authorization token option value
    Query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'oliver_pos_auth_token' (adjust prefix if different). Also check if the option exists at all.
    Affected if The oliver_pos_auth_token option is missing, empty, or evaluates to false/null (indicating a fresh or incompletely configured installation)
  3. Verify REST API authentication bypass
    Send a crafted request to the Oliver POS REST API endpoint (typically /wp-json/oliver/v1/ or similar) with the header 'OliverAuth: 0' and observe if the request is accepted without valid credentials.
    Affected if The REST API accepts the request with 'OliverAuth: 0' and returns data or actions that should require authentication
  4. Confirm plugin version against fixed release
    Compare the installed plugin version to the latest version on the WordPress repository or the vendor's release notes to confirm whether the strict comparison fix has been applied.
    Affected if The installed version predates the patch that replaced loose (==) comparison with strict (===) and added proper null/false handling

A user is affected if the Oliver POS plugin is installed, the authorization token option is unset or evaluates to false, and the REST API accepts 'OliverAuth: 0' as valid authentication, allowing unauthenticated access to sensitive user data and administrative functions.

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 plugin to the latest version once available. Ensure the admin completes the connection flow to set the authorization token, which prevents the false comparison trigger.

Recommended fix High confidence
  1. 1. Contact the plugin vendor (Oliver POS) directly through their support channels or WordPress plugin repository to request an emergency security patch.
  2. 2. As a temporary mitigation, consider disabling the Oliver POS plugin until a security update is available.
  3. 3. Implement additional firewall rules or web application firewall (WAF) configurations to block requests to /wp-json/pos-bridge/* endpoints from untrusted sources.
  4. 4. Monitor access logs for any suspicious requests containing the 'OliverAuth' header, especially with value '0'.
  5. 5. Restrict access to the /wp-json/pos-bridge/ API namespace at the web server level (Apache/Nginx) to limit exposure.
  6. 6. Ensure WordPress users with administrator roles have strong, unique passwords and enable two-factor authentication to mitigate potential account takeover attempts described in the advisory.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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