sales@hackhalt.com

Home / Threats / CVE-2026-14205

WP Events Manager - Improper Input Validation (CVE-2026-14205)

CVE-2026-14205

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.

CVE-2026-14205

CRITICAL CVSS 9.8 Published 2026-08-07 Updated 2026-08-26
AI Risk Critical (90/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P1 Immediate
Severity Band CRITICAL
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Components 1
Reference Links 1
AI Risk Engine Critical (90/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-08-07 CVE published and first recorded in the threat feed.
  2. 2026-08-26 Record updated with latest vulnerability metadata.
  3. 2026-08-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 43 days ago

AI enriched 43 days ago (2026-08-09 08:33 UTC)

Technical Summary

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.

Potential Impact

Severity is CRITICAL (CVSS 9.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 90/100 (Critical, High) with priority P1 Immediate. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

WP Events Manager PLUGIN · wp-events-manager Affected: < 2.2.5 Fixed in: 2.2.5

References

What to do about this

Patch immediately Serious, and reachable without meaningful privilege.

Fix it

Update WP Events Manager to 2.2.5 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs WP Events Manager, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs WP Events Manager. Versions below 2.2.5 are vulnerable; that release and later are not. An attacker needs any registered account, so open registration materially increases the risk.

How do I fix it?

Update WP Events Manager to version 2.2.5 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Improper Input Validation flaw. An attacker who exploits it can submit values the application never expected, with effects that vary by feature.