# CVE-2026-14205: WP Events Manager < 2.2.5 - Subscriber+ Payment Bypass via 'qty' Parameter

> Authenticated users can bypass payment for paid events by manipulating the quantity parameter, allowing unauthorized bookings.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-xm6j-g6w8-55mf

## What is CVE-2026-14205?

CVE-2026-14205 is a critical vulnerability in Unknown WP Events Manager, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Events Manager WordPress plugin before 2.2.5 does not validate the requested quantity when registering for a paid event and computes the price from the attacker-controlled quantity, allowing any authenticated user to create a completed booking for a paid event without making a payment.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-14205?


## How do I fix CVE-2026-14205?

No fix has been published for CVE-2026-14205 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14205 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14205 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14205 and fix it if it is affected.

What it is: CVE-2026-14205 is a critical vulnerability in Unknown WP Events Manager, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14205 exists.

Affected product: Unknown WP Events Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14205/ (Markdown: https://insights.sbomify.com/CVE-2026-14205/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14205
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14205
- OSV: https://osv.dev/vulnerability/CVE-2026-14205

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14205/
Summaries are generated and may contain mistakes; the official description above is the record.