CVE-2026-2694

The Events Calendar <= 6.15.16 - Improper Authorization to Authenticated (Contributor+) Event/Organizer/Venue Update/Trash via REST API

2026-02-25 08:50
type5afe

Strategic Overview

Status
Patched in 6.15.16.1
Affected Plugin
The Events Calendar
Affected Version
<= 6.15.16
CVSS
5.4Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2026-2694
View all The Events Calendar vulnerabilities

At a glance

CVE-2026-2694 is a medium-severity Improper Authorization vulnerability in the The Events Calendar WordPress plugin, affecting versions <= 6.15.16. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 6.15.16.1; sites on affected versions should update now. Disclosed February 2026, reported by type5afe.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-285: Improper Authorization

The Events Calendar <= 6.15.16 carries this weakness at can_edit, and reaching it takes an account at Contributor level or above. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For The Events Calendar the fix is 6.15.16.1: builds <= 6.15.16 are affected, anything from 6.15.16.1 onward is not.

Remediation

Update to version 6.15.16.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: The Events Calendar 6.15.16.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-2694https://www.wordfence.com/threat-intel/vulnerabilities/id/67351a37-a457-48d6-b40a-95a7e3a0d746https://nvd.nist.gov/vuln/detail/CVE-2026-2694

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C