CVE-2025-12407

Events Manager – Calendar, Bookings, Tickets, and more! <= 7.2.2.2 - Cross-Site Request Forgery to Location Deletion

2025-12-11 21:40
thinnawarth mathuros

Strategic Overview

Status
Patched in 7.2.2.3
Affected Version
<= 7.2.2.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-12407
View all Events Manager – Calendar, Bookings, Tickets, and more! vulnerabilities

At a glance

CVE-2025-12407 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Events Manager WordPress plugin, affecting versions <= 7.2.2.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.2.2.3; sites on affected versions should update now. Disclosed December 2025, reported by thinnawarth mathuros.

Vulnerability Overview

The Events Manager – Calendar, Bookings, Tickets, and more! plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 7.2.2.2. This is due to missing or incorrect nonce validation on the 'location_delete' action. This makes it possible for unauthenticated attackers to delete locations via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Events Manager <= 7.2.2.2 carries this weakness at location_delete, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Events Manager the fix is 7.2.2.3: builds <= 7.2.2.2 are affected, anything from 7.2.2.3 onward is not.

Remediation

Update to version 7.2.2.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Events Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Events Manager 7.2.2.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C