WordPress security changelog
MEDIUM CVE-2026-15023 Deferred

Events Manager permits Contributor-level second-order SQL injection

Events Manager through 7.4.0 lets a Contributor or higher store SQL metacharacters in a custom meta_key and then invoke event_duplicate or location_duplicate. Those actions read stored keys through get_post_meta() and concatenate them into an INSERT query, producing second-order SQL injection that can extract sensitive database information.

CVE / CNA score 6.5 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Events Manager – Calendar, Bookings, Tickets, and more!
Plugin slug
events-manager
Affected
<= 7.4.0
Safe version
7.4.1
Published
Aug 25, 2026
Weakness
CWE-89 — Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

This CVE was published Aug 25, 2026 and is one of 46 known issues for this plugin.

What to do

Update, patch or deactivate.

Update to 7.4.1 or later and review post metadata, event and location duplication activity, and database logs for suspicious values or queries.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Events Manager – Calendar, Bookings, Tickets, and more! plugin for WordPress is vulnerable to generic SQL Injection via Stored 'meta_key' via Event/Location Duplicate Action in all versions up to, and including, 7.4.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is a second-order SQL injection: an attacker first plants SQL metacharacters in a custom meta key via the standard add-meta flow (WordPress stores these verbatim in wp_postmeta), then triggers the injection by invoking the event_duplicate or location_duplicate action, which reads the stored meta keys via get_post_meta() and concatenates them unsafely into the INSERT query.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

References

Primary and upstream sources