WordPress WpEvently plugin <= 5.1.1 - PHP Object Injection vulnerability

published 2026-02-19 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-7988

cvss: 9.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits: 0; none known

Deserialization of Untrusted Data vulnerability in magepeopleteam WpEvently mage-eventpress allows Object Injection.This issue affects WpEvently: from n/a through <= 5.1.1.

Patch / fix

fixed in 1

magepeopleteam WpEvently 5.1.2

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 8 mo ago (2026-02-19)

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

magepeopleteam WpEvently

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/Wordpress/Plugin/mage-eventpress/vulnerability/wordpress-wpevently-plugin-5-1-1-php-object-injection
vdb-entry

Sources

CVE List CVE-2026-23549
NVD CVE-2026-23549

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary