Unauthenticated API access via loose token comparison
Published May 20, 2026 · Updated May 20, 2026
Authorization bypass in Oliver POS 2.4.2.6 and earlier allows remote attackers to access POS REST API endpoints without authentication. The oliver_pos_rest_authentication() callback loosely compares the OliverAuth header with an unset option whose false value equals the string 0 under PHP type juggling. Fresh installations with an incomplete connection flow expose user reads, profile changes, non-admin deletion, and administrator email reset that enables site takeover.
Summary
What happened
Authorization bypass in Oliver POS 2.4.2.6 and earlier allows remote attackers to access POS REST API endpoints without authentication. The oliver_pos_rest_authentication() callback loosely compares the OliverAuth header with an unset option whose false value equals the string 0 under PHP type juggling. Fresh installations with an incomplete connection flow expose user reads, profile changes, non-admin deletion, and administrator email reset that enables site takeover.
The record
- CVE
- CVE-2026-6072
- Published
- May 20, 2026
- Updated
- May 20, 2026
- Vendor
- Oliver POS
- Product
- Oliver POS
- Classifications
- CWE-639, T1190, T1098
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2026CVE publishedPublication date reported by the CVE source.
- May 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.4.2.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo