LiveActive security incident?Get immediate response
CVE Record

CVE-2024-24706: WordPress WP-CFM Plugin <= 1.7.8 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Forum One WP-CFM wp-cfm.This issue affects WP-CFM: from n/a through 1.7.8.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-24706 is a CSRF issue in the WordPress WP-CFM plugin through version 1.7.8. It may let an attacker trick a legitimate user into making unintended configuration-related changes. The rated impact is medium, with limited integrity and availability effects in the published CVSS data.

Executive priority

Treat this as a moderate-priority WordPress plugin issue. It is not evidenced as actively exploited in the supplied sources, but affected public sites should be identified and remediated during the next standard security update cycle.

Technical view

The vulnerability is CWE-352 Cross-Site Request Forgery in Forum One WP-CFM, package wp-cfm, affecting versions through 1.7.8. CVSS v3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, no confidentiality impact, and low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites running the WP-CFM plugin at version 1.7.8 or earlier. The source bundle does not identify affected managed hosting platforms, themes, or other plugins.

Exploitation context

The CVE is not marked as CISA KEV in the supplied data. The provided sources do not state active exploitation, public exploit availability, or specific attack campaigns. User interaction is required according to the CVSS vector.

Researcher notes

Evidence is strong for vulnerability class, affected product, affected range, and CVSS. Evidence is incomplete for fixed version, exploit details, and real-world exploitation. Avoid assuming impact beyond low integrity and low availability unless vendor details confirm affected actions.

Mitigation direction

  • Inventory WordPress sites for the WP-CFM plugin and record installed versions.
  • Prioritize sites running WP-CFM version 1.7.8 or earlier.
  • Check the vendor advisory and Patchstack entry for fixed versions or official mitigations.
  • Apply vendor-approved updates or mitigations after backup and change review.
  • Restrict administrative access and review high-risk plugin configuration workflows.

Validation and detection

  • Confirm whether WP-CFM is installed on each WordPress site.
  • Compare installed WP-CFM versions against the vulnerable range through 1.7.8.
  • Review vendor and Patchstack guidance for the current fixed-version status.
  • Check application logs for unexpected WP-CFM configuration changes.
  • Verify security controls that reduce CSRF risk around privileged WordPress sessions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2024-24706 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (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:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2024-24706Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Forum OneWP-CFMwp-cfm, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.