Live › vulnerability › CVE-2026-107649
Go to dashboardThe Events Made Easy plugin for WordPress up to and including 3.2.22 does not sanitize the event[location_name] parameter on guest event submissions. An unauthenticated attacker can plant script that runs in the browser of any visitor who opens the injected page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running Events Made Easy at version 3.2.22 or older with both guest event submission and forced location creation turned on. Both settings default to off, so most installs are not exposed. Sites that only display events created by staff are not exposed through this path.
No product ranges from the sources yet.
wp plugin get events-made-easy --field=version3.2.22, as soon as a patched release is published (the sources do not name one)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Events Made Easy plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event[location_name]' parameter in all versions up to, and including, 3.2.22 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only exploitable when both the guest event submission feature (eme_fs[guest_submit]) and forced location creation (eme_fs[force_location_creation]) are explicitly enabled by a site administrator, as both settings default to off.
This page as .md · .json · in your agent: get_signal("CVE-2026-107649")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.