CVE-2025-9808
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 The Events Calendar plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 6.15.2 via the REST endpoint. This makes it possible for unauthenticated attackers to extract information about password-protected vendors or venues.
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 Calendar WordPress plugin contains an information disclosure vulnerability in its REST API endpoint. Unauthenticated attackers can access the REST endpoint to retrieve details about password-protected vendors and venues that should require authentication to view. This represents a broken access control flaw in the REST API implementation.
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.
-
Confirm The Events Calendar plugin is installedNavigate to WordPress admin > Plugins and verify The Events Calendar appears in the installed plugins list, or check the plugin files in /wp-content/plugins/the-events-calendar/Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin > Plugins, click on The Events Calendar to view the version number, or inspect the main plugin file (e.g., the-events-calendar.php) for the 'Version' header commentAffected if The version is lower than 6.15.3 (e.g., 6.15.2, 6.14.x, earlier versions)
-
Test unauthenticated REST API access to vendor endpointsSend a GET request to /wp-json/tribe/v1/vendors or /wp-json/tribe/events/v1/vendors without providing authentication credentials (e.g., using curl or a browser)Affected if The endpoint returns vendor data without requiring authentication (HTTP 200 response with vendor details)
-
Test unauthenticated REST API access to venue endpointsSend a GET request to /wp-json/tribe/v1/venues or /wp-json/tribe/events/v1/venues without providing authentication credentialsAffected if The endpoint returns venue data without requiring authentication, including details about password-protected venues
A user is affected if The Events Calendar plugin version is below 6.15.3 AND the REST API endpoints are accessible without authentication, allowing exposure of password-protected vendor and venue information.
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 Calendar plugin to version 6.15.3 or later. If immediate update is not possible, consider restricting unauthenticated REST API access via server configuration or a security plugin.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9808 — 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-9808 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