CVE-2025-4796

Eventin <= 4.0.34 - Authenticated (Contributor+) Privilege Escalation via User Email Change/Account Takeover

2025-08-08 00:00
István Márton

Strategic Overview

Status
Patched in 4.0.35
Affected Version
<= 4.0.34
CVSS
8.8High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-4796
View all Eventin – Event Calendar, Tickets, Registration, Booking & WooCommerce vulnerabilities

At a glance

CVE-2025-4796 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the Eventin WordPress plugin, affecting versions <= 4.0.34. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.0.35; sites on affected versions should update now. Disclosed August 2025, reported by István Márton.

Vulnerability Overview

The Eventin plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 4.0.34. This is due to the plugin not properly validating a user's identity or capability prior to updating their details like email in the 'Eventin\Speaker\Api\SpeakerController::update_item' function. This makes it possible for unauthenticated attackers with contributor-level and above permissions to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Eventin <= 4.0.34 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Eventin the fix is 4.0.35: builds <= 4.0.34 are affected, anything from 4.0.35 onward is not.

Remediation

Update to version 4.0.35, 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: Eventin 4.0.35 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