This CVE exposes a price validation bypass in the native checkout flow of an event ticketing plugin that also supports WooCommerce integration. If your site uses the plugin's standalone checkout rather than WooCommerce checkout, an attacker can submit arbitrary price values and obtain tickets for free or at manipulated costs. The vulnerability is straightforward: the native checkout path trusts client-supplied price parameters instead of re-deriving the ticket price server-side from your event configuration. The WooCommerce-integrated path does this correctly — prices come from the cart and are validated by the payment gateway — but the separate native path was built without that enforcement layer. Check whether native checkout is enabled in your plugin settings. If it is, treat this as financially critical regardless of the CVSS 5.3 score, because exploitation is deterministic: anyone who sends the right payload gets free tickets. There is no rate limiting or anomaly detection mentioned in the disclosure that would catch this in flight. The patch adds server-side price re-derivation to the native checkout flow — verify you're on the patched version and audit your transaction logs for zero-cost or heavily discounted ticket orders as a one-time check for prior exploitation. If you cannot patch immediately, disable native checkout and route all purchases through WooCommerce, which retains the correct validation behavior. The EPSS score of 0.00236 reflects that automated scanning won't find this — exploitation requires understanding the plugin's specific checkout parameters and having valid event IDs — but the deterministic financial impact means the actual risk to your operation is higher than generic scoring suggests.
CVE-2026-16067
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 · uneditedThe Event Booking Manager for WooCommerce (Pro) WordPress plugin before 5.0.3 does not validate the ticket price on the server during its native (non-WooCommerce) checkout, trusting the per-ticket price supplied by the client instead of re-deriving the event's configured price. This allows unauthenticated users to book paid event tickets for free, obtaining completed bookings and valid tickets at no cost.
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 analysisA detailed technical summary for this CVE is being prepared.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 · scopedVersion 5.0.3 or later of Event Booking Manager for WooCommerce (Pro)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Event Booking Manager for WooCommerce (Pro)'
- 4. If an update is available, click 'Update Now' to upgrade to version 5.0.3 or later
- 5. Verify the update completed successfully
- 6. Test the booking process to confirm the fix is working (server now validates price rather than trusting client input)
- 7. If auto-update is not available, manually download the latest version from the plugin vendor or WordPress repository and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $1,600. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-16067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis CVE exposes a price validation bypass in the native checkout flow of an event ticketing plugin that also supports WooCommerce integration. If your site uses the plugin's standalone checkout rather than WooCommerce checkout, an attacker can submit arbitrary price values and obtain tickets for free or at manipulated costs. The vulnerability is straightforward: the native checkout path trusts client-supplied price parameters instead of re-deriving the ticket price server-side from your event configuration. The WooCommerce-integrated path does this correctly — prices come from the cart and are validated by the payment gateway — but the separate native path was built without that enforcement layer. Check whether native checkout is enabled in your plugin settings. If it is, treat this as financially critical regardless of the CVSS 5.3 score, because exploitation is deterministic: anyone who sends the right payload gets free tickets. There is no rate limiting or anomaly detection mentioned in the disclosure that would catch this in flight. The patch adds server-side price re-derivation to the native checkout flow — verify you're on the patched version and audit your transaction logs for zero-cost or heavily discounted ticket orders as a one-time check for prior exploitation. If you cannot patch immediately, disable native checkout and route all purchases through WooCommerce, which retains the correct validation behavior. The EPSS score of 0.00236 reflects that automated scanning won't find this — exploitation requires understanding the plugin's specific checkout parameters and having valid event IDs — but the deterministic financial impact means the actual risk to your operation is higher than generic scoring suggests.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-16067 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
- 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