Web
CVE-2026-24954
Deserialization (Object Injection) in WpEvently mage-eventpress ≤5.0.8.
- CVSS
- 8.8Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.43%chance of exploitation in the next 30 daystop 63% of scored CVEsFIRST score of 14 Nov 2026
- Fix
- Not stated by the vendorno fixed release in the CVE record
- Published
- 3 Feb 2026analysed here 4 Feb 2026
Summary
Impact
Remote code execution via crafted serialized data in WordPress plugin WpEvently mage-eventpress ≤5.0.8.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| magepeopleteam WpEvently | <= 5.0.8Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- WordPress WpEvently mage-eventpress <= 5.0.8
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? Partly. Insecure deserialization payloads can be built from many different gadget chains, so WAF signatures only catch the known ones.
Also consider: allow-list classes · patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 3 Feb 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 3 Feb 2026Published
- 3 Feb 2026CISA SSVC assessment: exploitation nonesame day later
- 4 Feb 2026Analysed by vulneraibility.comsame day later
- 28 Apr 2026CVE record last updated84 days (about 3 months) later
Common questions
Is CVE-2026-24954 being exploited?
Not confirmed. CVE-2026-24954 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-24954?
CVE-2026-24954 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-24954?
Not known from our data. No patch reference has been recorded for CVE-2026-24954, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-24954 affect?
CVE-2026-24954 affects WordPress WpEvently mage-eventpress <= 5.0.8. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-24954?
Patch when available or disable the plugin until fixed
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Other links (1)
- patchstack.com /database/Wordpress/Plugin/mage-eventpress/vulnerability/wordpress-wpevently-plu
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.