Eventin <= 4.1.29 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via 'id' Parameter
Strategic Overview
- Status
- Patched in 4.1.30
- Affected Version
<= 4.1.29- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-109994
At a glance
CVE-2026-109994 is a medium-severity Missing Authorization vulnerability in the Eventin WordPress plugin, affecting versions <= 4.1.29. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.1.30; sites on affected versions should update now. Disclosed November 2026, reported by Wordfence PRISM.
Vulnerability Overview
The Eventin – Events Calendar, Tickets, Registration, Booking & WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.1.29 via the 'id' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract the email address and phone number of any WordPress user, including administrators, by supplying their user id in a query-string parameter while placing the authenticated user's own id in the URL path.
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.
CWE-862: Missing Authorization
Reaching this weakness in Eventin <= 4.1.29 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 Eventin the fix is 4.1.30: builds <= 4.1.29 are affected, anything from 4.1.30 onward is not.
Remediation
Update to version 4.1.30, 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.1.30 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 9.8CVE-2025-47539: Eventin <= 4.0.26 Unauthenticated Privilege Escalation
CVE-2025-47539 - 7.2CVE-2025-14657: Eventin Unauthenticated Stored XSS
CVE-2025-14657 - 5.4CVE-2026-11821: Eventin Authenticated (Subscriber+) Notification Flow
CVE-2026-11821 - 5.3CVE-2026-110380: Eventin Missing Authorization
CVE-2026-110380
Other vulnerabilities in Eventin – Events Calendar, Tickets, Registration, Booking & WooCommerce
- 8.8CVE-2025-4796: Eventin <= 4.0.34 Privilege Escalation
CVE-2025-4796 - 8.8CVE-2025-39584: Eventin <= 4.0.25 Local File Inclusion
CVE-2025-39584 - 8.8CVE-2025-1770: Event Manager LFI
CVE-2025-1770 - 8.8CVE-2025-26964: Eventin <= 4.0.20 Local File Inclusion
CVE-2025-26964 - 8.8CVE-2024-56213: Eventin <= 4.0.7 Local File Inclusion
CVE-2024-56213 - 8.8CVE-2024-7149: Event Manager LFI
CVE-2024-7149 - 7.5CVE-2026-75983: Eventin Privilege Escalation
CVE-2026-75983 - 7.5CVE-2026-15667: Eventin <= 4.1.22 Local File Inclusion
CVE-2026-15667
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C