Event Booking Manager for WooCommerce – Sell Tickets, Event Registration, RSVP & Event Calendar

mage-eventpress · plugin

Known security vulnerabilities for Event Booking Manager for WooCommerce – Sell Tickets, Event Registration, RSVP & Event Calendar. Find out in seconds which version runs on your site with WP Lens.

25 known vulnerabilities

1 critical · 10 exploitable without logging in · latest Sep 8, 2026

Listed on wordpress.org · latest 5.7.5 · last updated Sep 29, 2026 · 7K+ installs

wordpress.org status checked on Oct 2, 2026

Vulnerabilities

CVE-2026-23549unauthenticated≤ 5.1.1
WordPress WpEvently plugin <= 5.1.1 - PHP Object Injection vulnerability
Critical 9.8
CVE-2026-24954login required≤ 5.0.8
WordPress WpEvently plugin <= 5.0.8 - Deserialization of untrusted data vulnerability
High 8.8
CVE-2025-54742login required≤ 4.4.8
WordPress WpEvently Plugin <= 4.4.8 - PHP Object Injection Vulnerability
High 8.8
CVE-2025-32145login required≤ 4.3.6
WordPress WpEvently plugin <= 4.3.6 - PHP Object Injection vulnerability
High 8.8
CVE-2024-43138login required≤ 4.2.1
WordPress Event Manager and Tickets Selling Plugin for WooCommerce plugin <= 4.2.1 - Local File Inclusion vulnerability
High 8.8
CVE-2024-24796login required≤ 4.1.1
WordPress Event Manager for WooCommerce Plugin <= 4.1.1 is vulnerable to PHP Object Injection
High 8.8
CVE-2022-47164login required≤ 3.7.7
WordPress Event Manager for WooCommerce Plugin <= 3.7.7 is vulnerable to Cross Site Request Forgery (CSRF)
High 8.8
CVE-2026-45441unauthenticated≤ 5.3.3
WordPress WpEvently plugin <= 5.3.3 - Other Vulnerability Type vulnerability
High 7.5
CVE-2025-30895login required≤ 4.2.9
WordPress WpEvently Plugin <= 4.2.9 - PHP Object Injection vulnerability
High 7.5
CVE-2026-25361unauthenticated · needs a click≤ 5.1.4
WordPress WpEvently plugin <= 5.1.4 - Reflected Cross Site Scripting (XSS) vulnerability
High 7.1
CVE-2026-81802unauthenticated≤ 5.6.0
WordPress WpEvently plugin <= 5.6.0 - Insecure Direct Object References (IDOR) vulnerability
Medium 6.5
CVE-2024-49703login required≤ 4.2.5
WordPress WpEvently plugin <= 4.2.5 - Cross Site Scripting (XSS) vulnerability
Medium 6.5
CVE-2026-81759contributor+≤ 5.5.0
WordPress WpEvently plugin <= 5.5.0 - Broken Access Control vulnerability
Medium 5.4
CVE-2025-5568contributor+≤ 4.4.2
WpEvently <= 4.4.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
Medium 5.4
CVE-2023-36383editor+≤ 3.9.5
WordPress Event Manager for WooCommerce Plugin <= 3.9.5 is vulnerable to Cross Site Scripting (XSS)
Medium 5.4
CVE-2026-32354unauthenticated≤ 5.1.9
WordPress WpEvently plugin < 5.1.9 - Sensitive Data Exposure vulnerability
Medium 5.3
CVE-2025-66083unauthenticated≤ 5.0.4
WordPress WpEvently plugin <= 5.0.4 - Broken Access Control vulnerability
Medium 5.3
CVE-2025-66082unauthenticated≤ 5.0.4
WordPress WpEvently plugin <= 5.0.4 - Broken Access Control vulnerability
Medium 5.3
CVE-2025-30887unauthenticated≤ 4.2.9
WordPress WpEvently Plugin <= 4.2.9 - Broken Access Control vulnerability
Medium 5.3
CVE-2023-28422admin≤ 3.8.6
WordPress Event Manager for WooCommerce Plugin <= 3.8.6 is vulnerable to Cross Site Scripting (XSS)
Medium 4.8
CVE-2024-32110unauthenticated · needs a click≤ 4.1.2
WordPress Event Manager and Tickets Selling Plugin for WooCommerce plugin <= 4.1.2 - Cross Site Request Forgery (CSRF) vulnerability
Medium 4.3
CVE-2026-24942unauthenticated · needs a click≤ 5.1.1
WordPress WpEvently plugin <= 5.1.1 - Cross Site Request Forgery (CSRF) vulnerability
Medium 4.3
CVE-2026-81761subscriber+≤ 5.5.0
WordPress WpEvently plugin <= 5.5.0 - Broken Access Control vulnerability
Medium 4.3
CVE-2025-54705login required≤ 4.4.6
WordPress WpEvently plugin <= 4.4.6 - Broken Access Control vulnerability
Medium 4.3
CVE-2026-17166contributor+≤ 5.3.7
Event Booking Manager for WooCommerce <= 5.3.7 - Missing Authorization to Authenticated (Contributor+) Site-Wide Payment Settings Modification via mep_save_paym
Medium 4.3

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory