dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-2694

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The The Events Calendar plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to an improper capability check on the 'can_edit' and 'can_delete' function in all versions up to, and including, 6.15.16. This makes it possible for authenticated attackers, with Contributor-level access and above, to update or trash events, organizers and venues via REST API.

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 · moderate confidence

The Events Calendar WordPress plugin has improper capability checks in its REST API 'can_edit' and 'can_delete' functions, allowing authenticated Contributor-level users to modify or trash events, organizers, and venues outside their authorized scope due to missing authorization validation in the API endpoints.

MitigationUpdate to version 6.15.17 or later which patches the capability checks. Audit user roles and REST API access permissions in the interim.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check The Events Calendar plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'The Events Calendar'. The version number is displayed below the plugin name. Alternatively, check the file 'wp-content/plugins/the-events-calendar/common/lib/Version.php' or the plugin's readme.txt for the version header.
    Affected if The installed version is earlier than 6.15.17
  2. Verify REST API is accessible
    Send a GET request to your site's /wp-json/tribe/events/v1/ endpoint using curl or a browser. A successful response with JSON event data indicates the REST API is active.
    Affected if The REST API endpoint returns HTTP 200 with event data (API must be enabled for the vulnerability to apply)
  3. Check for Contributor-level users
    In WordPress admin, go to Users > All Users and review the 'Role' column. Alternatively, query the wp_usermeta table for entries where meta_key = 'wp_capabilities' and meta_value contains 'contributor'.
    Affected if There is at least one user with the Contributor role active on the site
  4. Verify Contributor role permissions on events
    As a Contributor user, attempt to access the REST API endpoint to modify an event you did not create (e.g., send a DELETE request to /wp-json/tribe/events/v1/events/{event-id} for an event created by another user).
    Affected if The API request succeeds (returns 200 or 204) when a Contributor deletes or modifies an event they did not author, indicating the authorization bypass is present

You are affected if your Events Calendar version is below 6.15.17, the REST API is enabled, and you have Contributor-level users who can modify or delete events they did not create.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 6.15.17 or later which patches the capability checks. Audit user roles and REST API access permissions in the interim.

Recommended fix Moderate confidence

Upgrade to a version newer than 6.15.16 (the vendor has released a patch in a subsequent version)

  1. Check the current version of The Events Calendar plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. If the installed version is 6.15.16 or lower, update the plugin to the latest available version
  4. After updating, verify the fix by confirming the REST API properly enforces authorization checks for the 'can_edit' and 'can_delete' functions
  5. Test that Contributor-level users can no longer update or delete events, organizers, or venues via REST API without proper permissions
  6. Review user role capabilities to ensure only users with appropriate permissions (like Events Pro or higher) can modify events
Caveat Review any plugin functionality changes after upgrade as minor version updates may include feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2694 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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