LiveActive security incident?Get immediate response
CVE Record

CVE-2024-24872: WordPress Themify Builder Plugin <= 7.0.5 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Themify Themify Builder.This issue affects Themify Builder: from n/a through 7.0.5.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-24872 is a CSRF issue in the WordPress Themify Builder plugin through version 7.0.5. An attacker could trick a user into making an unintended change, but the published scoring indicates low integrity impact and no confidentiality or availability impact.

Executive priority

Treat as moderate priority. Address during the next plugin maintenance window, sooner for public, business-critical WordPress sites.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in Themify Builder up to 7.0.5. CVSS 3.1 is 4.3: network reachable, low attack complexity, no attacker privileges required, user interaction required, unchanged scope, and low integrity impact only.

Likely exposure

Exposure is limited to WordPress installations using Themify Builder version 7.0.5 or earlier. The source bundle does not identify specific vulnerable actions, required victim role, or affected configurations beyond the plugin and version range.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires user interaction. Public details are sparse, so defenders should avoid assuming broad compromise without local evidence.

Researcher notes

The source bundle confirms the vulnerability class, product, affected upper version, CVSS vector, and non-KEV status. It does not provide endpoint details, proof-of-concept status, patch version, or mitigation specifics, so validation should stay evidence-based and vendor-guided.

Mitigation direction

  • Inventory WordPress sites for Themify Builder installations and versions.
  • Prioritize updates or vendor guidance for versions 7.0.5 and earlier.
  • Limit administrative access to trusted users until reviewed.
  • Monitor Patchstack and Themify advisories for confirmed fixed versions.
  • Review recent site changes for unauthorized builder configuration updates.

Validation and detection

  • Confirm whether Themify Builder is installed on each WordPress site.
  • Record the installed plugin version and compare it with 7.0.5.
  • Check CVE and Patchstack records for updated remediation guidance.
  • Review audit logs for unexpected content or configuration changes.
  • Perform only authorized benign CSRF-control checks in staging.
Prepared
Confidence
medium
Sources
3

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-24872 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
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

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
2Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-24872Attack 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:N

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
ThemifyThemify Builderthemify-builder, 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.