CVE-2025-14507
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 EventPrime - Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.2.7.0 via the REST API. This makes it possible for unauthenticated attackers to extract sensitive booking data including user names, email addresses, ticket details, payment information, and order keys when the API is enabled by an administrator. The vulnerability was partially patched in version 4.2.7.0.
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 EventPrime WordPress plugin has a broken access control vulnerability in its REST API endpoints. When the API is enabled by an administrator, unauthenticated attackers can query booking endpoints to extract sensitive customer data including names, emails, ticket details, payment information, and order keys without any authentication or authorization checks.
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.
-
Check if EventPrime plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for EventPrime, or check the wp-content/plugins directory for the eventprime folder. Note the installed version from the plugin description.Affected if EventPrime plugin is installed and the version is lower than the patched version (when known)
-
Verify if EventPrime REST API is enabledIn WordPress admin, navigate to EventPrime > Settings > General or API settings. Look for a REST API or API Enable option. Check if it is toggled to ON or enabled.Affected if The REST API setting is enabled (ON/enabled)
-
Test unauthenticated access to booking endpointsUsing a tool like curl or a browser, send a GET request to the EventPrime booking endpoints without providing any authentication. Common endpoints include /wp-json/ep/bookings or /wp-json/ep/booking-data. Example: curl -s https://yourdomain.com/wp-json/ep/bookingsAffected if The request returns booking data, customer names, emails, or order information without requiring login credentials
-
Check for sensitive data exposure in API responseExamine the response from the unauthenticated API call. Look for fields containing customer PII such as names, email addresses, ticket details, payment information, or order keys.Affected if The API response contains any customer PII, booking details, payment data, or order keys without authentication
A user is affected if the EventPrime plugin is installed, its REST API is enabled, and booking endpoints are accessible without authentication exposing customer data.
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 dataDisable the EventPrime REST API if not needed, or update to the latest version when available. Until fully patched, consider restricting API access via server-side rules or web application firewall configurations.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14507 — 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-14507 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