CVE-2025-12408

Events Manager <= 7.2.2.2 - Unauthenticated Information Exposure

2025-12-11 21:39
thinnawarth mathuros

Strategic Overview

Status
Patched in 7.2.2.3
Affected Plugin
Events Manager – Calendar, Bookings, Tickets, and more!
Affected Version
<= 7.2.2.2
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-12408
View all Events Manager – Calendar, Bookings, Tickets, and more! vulnerabilities

At a glance

CVE-2025-12408 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Events Manager WordPress plugin, affecting versions <= 7.2.2.2. It carries a CVSS score of 5.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 Information Exposure in all versions up to, and including, 7.2.2.2 via the 'get_location' action due to insufficient restrictions on which locations can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft event locations that they should not have access to.

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, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Events Manager <= 7.2.2.2 carries this weakness at get_location, and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. 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?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. 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.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12408https://www.wordfence.com/threat-intel/vulnerabilities/id/8470b7be-6fae-4941-b523-93e230366522https://nvd.nist.gov/vuln/detail/CVE-2025-12408

Related records

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