Security readout for executives and security teams
Plain-English summary
CVE-2024-32110 is a CSRF flaw in Magepeople WpEvently, also listed as the WordPress Event Manager and Tickets Selling Plugin for WooCommerce. Affected versions are through 4.1.2. It could let an attacker trick a site user into causing an unintended low-impact change. Sources do not describe active exploitation or a fixed version.
Executive priority
Treat as a targeted WordPress hygiene issue, not an emergency. Prioritize affected commerce or event-registration sites because unintended integrity changes can affect customer-facing operations, but current evidence does not support crisis handling.
Technical view
The issue is CWE-352 cross-site request forgery in the WordPress plugin package mage-eventpress. CVSS 3.1 is 4.3 with network attack vector, low complexity, user interaction required, no confidentiality impact, low integrity impact, and no availability impact. The public bundle does not identify the vulnerable endpoint, action, nonce failure, or patch details.
Likely exposure
Exposure is limited to WordPress sites running Magepeople WpEvently / mage-eventpress at version 4.1.2 or earlier. Sites not using this plugin are unaffected per the bundle's default status. The exact affected admin or user workflow is not specified.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. CSRF generally depends on a victim interacting with attacker-controlled content while authenticated, but the specific action and required victim role are not documented here.
Researcher notes
Public details are sparse. The bundle confirms CSRF, affected versions through 4.1.2, CVSS 4.3, and Patchstack as the VDB reference. It does not provide endpoint names, proof of exploitation, exploit maturity, affected roles, or remediation version.
Mitigation direction
- Inventory WordPress sites for mage-eventpress or WpEvently installations.
- Check plugin version and flag any deployment at 4.1.2 or earlier.
- Review vendor or Patchstack guidance for a fixed release or official workaround.
- If no fix is available, consider disabling the plugin where business impact permits.
- Warn administrators against interacting with unsolicited links while logged into WordPress.
Validation and detection
- Confirm whether the site uses Magepeople WpEvently / mage-eventpress.
- Record the installed plugin version from WordPress administration or asset inventory.
- Review WordPress activity logs for unexpected plugin-related changes.
- Confirm whether vendor guidance identifies a patched version or workaround.
- Track CISA KEV and vendor advisories for any change in exploitation status.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-32110 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4PatchstackVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.