Security readout for executives and security teams
Plain-English summary
CVE-2024-24929 is a CSRF issue in the WordPress WP Contact Form plugin through version 1.6. An attacker would need to trick a user into taking an action, and the documented impact is limited integrity impact, not data theft or service outage.
Executive priority
Treat this as a moderate WordPress plugin hygiene issue. It is not evidenced as actively exploited in the provided sources, but affected sites should be remediated during normal maintenance, faster for business-critical public WordPress sites.
Technical view
The sources identify CWE-352 Cross-Site Request Forgery in Ryan Duff/Peter Westwood WP Contact Form up to version 1.6. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, and low integrity impact.
Likely exposure
Exposure is limited to WordPress sites running the WP Contact Form plugin version 1.6 or earlier. The source bundle does not identify affected CPEs, install counts, vulnerable actions, or a confirmed fixed version.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. CSRF generally depends on a victim user interacting while authenticated, but the bundle does not describe the specific forced action.
Researcher notes
Evidence is sparse. The bundle confirms CSRF classification, affected plugin and version range, and CVSS, but not the vulnerable endpoint, required victim role, exploit details, or fixed release. Avoid assuming broader impact without vendor detail.
Mitigation direction
- Inventory WordPress sites for WP Contact Form version 1.6 or earlier.
- Check Patchstack and vendor guidance for a fixed version or official mitigation.
- Update, disable, or replace the plugin if no maintained fix is available.
- Limit administrative access and require routine logout after privileged WordPress work.
- Prioritize sites where untrusted users can contact administrators frequently.
Validation and detection
- Confirm whether WP Contact Form is installed and record the exact version.
- Compare installed versions against the affected range: through 1.6.
- Check vendor or Patchstack advisory notes before changing production systems.
- After update or removal, verify contact form workflows still operate as intended.
- Review WordPress change logs for unexpected form or settings changes.
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-24929 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.4Primary CVE scoreVulnerability 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
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.