Security readout for executives and security teams
Plain-English summary
CVE-2026-2694 affects The Events Calendar WordPress plugin. A logged-in user with Contributor-level access or higher could modify or trash events, organizers, and venues through the REST API when they should not be authorized. This is primarily an integrity and availability risk for sites that allow contributor accounts.
Executive priority
Treat as a routine but time-bound WordPress remediation. Prioritize sites with contributor workflows, public event calendars, or many user accounts. It is not currently supported as actively exploited, but it can disrupt calendar content integrity.
Technical view
The issue is an improper authorization check, CWE-285, in can_edit and can_delete logic for REST API endpoints. Reported affected versions are The Events Calendar up to and including 6.15.16. CVSS 3.1 is 5.4: network-accessible, low complexity, low privileges required, no user interaction, with low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites running The Events Calendar through 6.15.16 that have Contributor or higher accounts, including potentially compromised accounts. Public visitor access alone is not enough based on the provided sources.
Exploitation context
The sources describe authenticated misuse via REST API but do not cite active exploitation. The CVE is not marked as CISA KEV in the provided bundle. Risk rises where many contributors exist or account compromise is plausible.
Researcher notes
Source evidence identifies authorization flaws in REST endpoints and references affected endpoint code plus a WordPress.org changeset. The provided bundle does not clearly name a fixed version, so remediation should be tied to vendor release notes or confirmed patched code.
Mitigation direction
- Identify WordPress sites using The Events Calendar.
- Check whether plugin version is 6.15.16 or older.
- Review vendor guidance and update when a fixed release is available.
- Restrict Contributor-level access to trusted users only.
- Monitor event, organizer, and venue changes for unauthorized edits or trashing.
Validation and detection
- Inventory plugin versions across WordPress environments.
- Confirm whether Contributor or higher accounts exist.
- Review REST API access logs for event, venue, or organizer update activity.
- Audit recent trashed or modified calendar content.
- Compare installed code against vendor changeset if assessing remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-2694 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/67351a37-a457-48d6-b40a-95a7e3a0d746?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/the-events-calendar/tags/6.15.16/src/Tribe/REST/V1/Endpoints/Single_Event.php#L563CVE reference
- https://plugins.trac.wordpress.org/browser/the-events-calendar/tags/6.15.16/src/Tribe/REST/V1/Endpoints/Single_Venue.php#L583CVE reference
- https://plugins.trac.wordpress.org/changeset/3468694/the-events-calendarCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.