Security readout for executives and security teams
Plain-English summary
This is a high-severity WordPress plugin issue in WpEvently through version 4.1.1. An authenticated low-privileged attacker may abuse unsafe PHP deserialization to compromise sensitive data or alter data, depending on reachable code paths. The source bundle does not confirm active exploitation.
Executive priority
Treat this as a near-term remediation item for WordPress environments using WpEvently. It is high severity, but evidence provided does not show active exploitation or a named patch, so prioritize inventory, vendor confirmation, and compensating controls.
Technical view
CVE-2024-24796 is CWE-502 deserialization of untrusted data in MagePeople Team Event Manager and Tickets Selling Plugin for WooCommerce, package mage-eventpress, affecting versions through 4.1.1. CVSS 3.1 is 8.2: AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N.
Likely exposure
Exposure is likely limited to WordPress sites running the WpEvently WooCommerce event plugin at version 4.1.1 or earlier. Other products or versions are not identified as affected in the supplied sources.
Exploitation context
The CVE is not listed as KEV in the supplied bundle. The CVSS vector indicates network reachability, low privileges required, high attack complexity, and no user interaction. No cited source confirms active exploitation, public exploit availability, or a complete exploit chain.
Researcher notes
The key uncertainty is exploitability in a specific deployment, because PHP object injection often depends on reachable deserialization paths and available object chains. The supplied sources identify the weakness and affected range but do not provide exploit status, proof details, or a confirmed fixed version.
Mitigation direction
- Inventory WordPress sites for the mage-eventpress or WpEvently plugin.
- Check MagePeople and Patchstack guidance for a fixed version or workaround.
- Upgrade the plugin if vendor guidance names a fixed release.
- Disable or remove the plugin where it is not business-critical.
- Restrict WordPress accounts to least privilege and review plugin access paths.
Validation and detection
- Confirm installed plugin name, package slug, and version on each WordPress site.
- Flag any WpEvently deployment at version 4.1.1 or earlier.
- Review WordPress users with low-privileged access to affected sites.
- Check security logs for suspicious authenticated plugin interactions.
- Document remediation status and any vendor guidance used.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-24796 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N1.85.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.