CVE-2026-6072
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk38th percentile - higher than 38% of all known CVEs
Summary
The Oliver POS plugin for WordPress up to version 2.4.2.6 has an authorization bypass vulnerability. The REST API authentication uses loose PHP comparison (==) for the 'OliverAuth' header. On fresh installations where the token option is unset, '0' == false evaluates to true, allowing unauthenticated full API access.
Risk Assessment
An unauthenticated attacker can gain full access to the POS API, read user data (including admins), modify user profiles (including email addresses), and delete non-admin users. Changing an admin email can lead to site takeover.
Recommendation
Update the Oliver POS plugin to the latest version immediately. Additionally, administrators should set the 'oliver_pos_authorization_token' option to a secure, non-empty token.
Original NVD description (English source)
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.