Event Espresso 4 Decaf – Event Registration Event Ticketing <= 4.10.46.decaf- Authenticated (Subscriber+) Missing Authorization to Limited Plugin Settings Modification
Strategic Overview
- Status
- Patched in 5.0.22.decaf
- Affected Plugin
- Event Espresso – Event Registration & Ticketing Sales
- Affected Version
<= 4.10.46.decaf- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-6883
At a glance
CVE-2024-6883 is a medium-severity Missing Authorization vulnerability in the Event Espresso WordPress plugin, affecting versions <= 4.10.46.decaf. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.0.22.decaf; sites on affected versions should update now. Disclosed August 2024, reported by Lucio Sá.
Vulnerability Overview
The Event Espresso 4 Decaf – Event Registration Event Ticketing plugin for WordPress is vulnerable to limited unauthorized plugin settings modification due to a missing capability check on the saveTimezoneString and some other functions in all versions up to and including 4.10.46.decaf. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify some of the plugin settings.
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-862: Missing Authorization
Reaching this weakness in Event Espresso <= 4.10.46.decaf takes an account at Subscriber level or above. 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.22.decaf: builds <= 4.10.46.decaf are affected, anything from 5.0.22.decaf onward is not.
Remediation
Update to version 5.0.22.decaf, 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: Event Espresso 5.0.22.decaf closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Event Espresso – Event Registration & Ticketing Sales
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C