Unauthenticated PHP object injection via untrusted deserialization
Published Feb 19, 2026 · Updated Feb 19, 2026
PHP object injection in MagePeople WPEvently 5.1.1 and earlier allows remote attackers to inject PHP objects via untrusted serialized input. The published records do not identify the request parameter, handler, or deserialization call that consumes the attacker-controlled value. No authentication is required; file deletion, data disclosure, or code execution requires a usable POP chain from another installed plugin or theme.
Summary
What happened
PHP object injection in MagePeople WPEvently 5.1.1 and earlier allows remote attackers to inject PHP objects via untrusted serialized input. The published records do not identify the request parameter, handler, or deserialization call that consumes the attacker-controlled value. No authentication is required; file deletion, data disclosure, or code execution requires a usable POP chain from another installed plugin or theme.
The record
- CVE
- CVE-2026-23549
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- MagePeople Team
- Product
- WPEvently
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=<= 5.1.1 changes=[{"at":"5.1.2","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo