CVE-2025-12408
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 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 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 analysis · high confidenceThe Events Manager WordPress plugin versions up to 7.2.2.2 have an unauthenticated information disclosure vulnerability in the 'get_location' action. The plugin fails to properly validate user permissions before returning location data, allowing unauthenticated attackers to query and extract sensitive details from password-protected, private, or draft event locations that should be restricted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Events Manager plugin is installedLog in to WordPress admin, go to Plugins, and check if 'Events Manager' appears in the list of installed plugins.Affected if The plugin is not installed on the WordPress site.
-
Check installed version of Events ManagerIn WordPress admin > Plugins, locate Events Manager and read the version number displayed under the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/events-manager/em-loader.php or similar main file for the 'Version' comment.Affected if The installed version is 7.2.2.2 or earlier.
-
Confirm the get_location action endpoint exists and is accessibleMake an unauthenticated HTTP request to the WordPress AJAX endpoint (typically /wp-admin/admin-ajax.php?action=get_location) or check the plugin source code for the registered 'get_location' action handler in the AJAX hooks.Affected if The endpoint responds and the action is registered without capability checks.
-
Test unauthenticated access to location dataSend a crafted request to the get_location endpoint with an event ID that corresponds to a password-protected, private, or draft event. Observe if the response returns location details (address, coordinates, map URL) without requiring authentication.Affected if Location data for restricted events is returned to unauthenticated users.
A site is affected if Events Manager version 7.2.2.2 or earlier is installed and the get_location action exposes data from password-protected, private, or draft events to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the Events Manager plugin to version 7.2.3 or later. As an interim measure, restrict access to the affected endpoint via web server configuration or implement IP-based access controls until the patch can be applied.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12408 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12408 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
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
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