Cyber Resilience

CVE-2024-37437

Path Traversal in Elementor Website Builder ≤ 3.22.2

Path TraversalXSS
Published
09 July 2024
Modified
23 April 2026
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L
EPSS Score 0.0034 26th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2024-37437 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Elementor Website Builder. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access ControlA05:2025 Injection

EU & UK References

Vulnerability Data

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Elementor Elementor Website Builder elementor.This issue affects Elementor Website Builder: from n/a through <= 3.22.1.

CWE(s)
CWE-79CWE-22

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
attack.mitre.org →
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-47505Same product: Elementor Website Builder
CVE-2023-5005Same product class: WordPress / CMS plugin
CVE-2023-0585Same product class: WordPress / CMS plugin
CVE-2023-40680Same product class: WordPress / CMS plugin
CVE-2023-47547Same product class: WordPress / CMS plugin
CVE-2023-47680Same product class: WordPress / CMS plugin
CVE-2023-1159Same product class: WordPress / CMS plugin
CVE-2023-30871Same product class: WordPress / CMS plugin
CVE-2023-41662Same product class: WordPress / CMS plugin
CVE-2023-49181Same product class: WordPress / CMS plugin

Affected Assets

elementor
website builder
≤ 3.22.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2
  • V1.1.2
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.

SI-10 Information Input Validation good match

Input validation directly enforces neutralization of untrusted data before it reaches web output generation.

SI-15 Information Output Filtering good match

Output filtering can catch or sanitize unneutralized script content before it is served to users.

AC-6 Least Privilege partial match

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

A.5.6 Contact with special interest groups partial match
prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

A.5.7 Threat intelligence partial match
prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

A.8.25 Secure development life cycle partial match
prevents

Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for safe file handling and canonicalization.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require least-privilege file access and directory isolation.

References