Payment bypass via unbound authorization token
Published Aug 6, 2026 · Updated Aug 6, 2026
Authorization bypass in Events Made Easy before 3.1.2 allows remote attackers to mark higher-priced bookings as fully paid. The payment charging and notification flow accepts an authorization token without verifying that its authorized amount matches the payment record being credited. No account or user interaction is required; exploitation pays for a cheaper booking before applying that authorization to a separate, costlier booking.
Summary
What happened
Authorization bypass in Events Made Easy before 3.1.2 allows remote attackers to mark higher-priced bookings as fully paid. The payment charging and notification flow accepts an authorization token without verifying that its authorized amount matches the payment record being credited. No account or user interaction is required; exploitation pays for a cheaper booking before applying that authorization to a separate, costlier booking.
The record
- CVE
- CVE-2026-14842
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Franky Van Liedekerke
- Product
- Events Made Easy
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 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 <3.1.2
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