CVE-2025-68007

Event Espresso 4 Decaf <= 5.0.37.decaf - Missing Authorization to Unauthenticated Settings Change

2026-01-15 00:00
Legion Hunter

Strategic Overview

Status
Patched in 5.0.53.decaf
Affected Version
<= 5.0.37.decaf
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-68007
View all Event Espresso – Event Registration & Ticketing Sales vulnerabilities

At a glance

CVE-2025-68007 is a medium-severity Missing Authorization vulnerability in the Event Espresso WordPress plugin, affecting versions <= 5.0.37.decaf. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.0.53.decaf; sites on affected versions should update now. Disclosed January 2026, reported by Legion Hunter.

Vulnerability Overview

The Event Espresso – Event Registration & Ticketing Sales plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 5.0.37.decaf. This makes it possible for unauthenticated attackers to perform an unauthorized action.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Event Espresso <= 5.0.37.decaf takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Event Espresso the fix is 5.0.53.decaf: builds <= 5.0.37.decaf are affected, anything from 5.0.53.decaf onward is not.

Remediation

Update to version 5.0.53.decaf, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Event Espresso 5.0.53.decaf closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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