CVE-2026-6072

Oliver POS <= 2.4.2.6 - Unauthenticated Authorization Bypass Through User-Controlled Key to 'OliverAuth' Header

2026-05-19 12:03
Hunter Jensen (skid)

Strategic Overview

Status
Patched in 4.5.4
Affected Version
<= 2.4.2.6
CVSS
6.5Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-6072
View all Oliver POS – WooCommerce POS for iPhone, iPad & Android vulnerabilities

At a glance

CVE-2026-6072 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Oliver POS WordPress plugin, affecting versions <= 2.4.2.6. It carries a CVSS score of 6.5 (reachable over the network; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.5.4; sites on affected versions should update now. Disclosed May 2026, reported by Hunter Jensen (skid).

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-639: Authorization Bypass Through User-Controlled Key

Oliver POS <= 2.4.2.6 carries this weakness at OliverAuth, and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Oliver POS the fix is 4.5.4: builds <= 2.4.2.6 are affected, anything from 4.5.4 onward is not.

Remediation

Update to version 4.5.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Oliver POS 4.5.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C