CVE-2024-13353
Cyberchimps Responsive Addons For Elementor ≤ 1.6.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-13353 is a high-severity PHP Remote File Inclusion (CWE-98) vulnerability in Cyberchimps Responsive Addons For Elementor. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Software Extensions (T1176); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-13353 is a Local File Inclusion (LFI) vulnerability in the Responsive Addons for Elementor – Free Elementor Addons Plugin and Elementor Templates plugin for WordPress, affecting all versions up to and including 1.6.4. The flaw resides in several widgets, enabling the inclusion and execution of arbitrary files on the server. It carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and is linked to CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program) and CWE-829 (Inclusion of Functionality from Untrusted Control Sphere).
Authenticated attackers with Contributor-level access or higher can exploit this vulnerability over the network with low complexity and no user interaction required. By targeting the affected widgets, they can include arbitrary server files containing PHP code for execution, bypassing access controls, extracting sensitive data, or achieving remote code execution—particularly when "safe" file types like images with embedded PHP are uploadable and subsequently included.
WordPress plugin trac references detail patches applied in version 1.6.5 via changeset 3226779, specifically addressing vulnerable code in files such as class-responsive-addons-for-elementor-product-carousel.php (line 3151 in trunk) and class-responsive-addons-for-elementor-woo-products.php (line 3725 in trunk). Wordfence's threat intelligence advisory confirms the issue and recommends updating to the patched version for mitigation.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4248
Vulnerability Data
The Responsive Addons for Elementor – Free Elementor Addons Plugin and Elementor Templates plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.6.4 via several widgets. This makes it possible for authenticated attackers,…
more
with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 6 OS baselines
V14.2.3V3.5.6V9.1.3V15.3.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing filename restrictions before deployment.
Validating all inputs before they reach include/require statements directly stops untrusted filenames from being used.
Requires documented, valid provenance for components, preventing acceptance of code from outside the trusted sphere.
Enforcing access authorizations on resources limits what an included file can reach even if a bad name is supplied.
Information-flow rules can block the loading of external or unauthorized files into the PHP process.
Implements detection and prevention of counterfeit or inauthentic components before they are integrated.
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.
Supply-chain program directly governs inclusion of third-party executable code.
Contractual requirements can mandate trusted sources and integrity checks for included functionality.
Supplier risk assessment explicitly covers risks from their products and libraries.
Software inventory enables tracking of externally sourced components but does not itself enforce trust.
Pre-acquisition integrity/authenticity checks directly prevent inclusion of untrusted code.
Critical-supplier assessment reduces risk of importing executable functionality from untrusted parties.
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.5.21's requirements to define/propagate security needs, obtain component origin/trust assurances, validate delivered products (incl. via testing), ensure genuine/unaltered components, and manage lifecycle directly stop most untrusted inclusion by shrinking the untrusted sphere before integration; bounded remainder exists for custom or insider-introduced functionality the clause does not reach.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248635 Executable search paths within the initialization files of all local interactive OL 8 users must only contain paths that resolve to the system default or the user's home directory. blocks CWE-829
Oracle Linux 9 (1 rule)
- V-271847 OL 9 must be configured so that executable search paths within the initialization files of all local interactive users must only contain paths that resolve to the system default or the users home directory. blocks CWE-829
RHEL 7 (1 rule)
- V-204477 The Red Hat Enterprise Linux operating system must be configured so that all local interactive user initialization files executable search paths contain only paths that resolve to the users home directory. blocks CWE-829
RHEL 8 (1 rule)
- V-230317 Executable search paths within the initialization files of all local interactive RHEL 8 users must only contain paths that resolve to the system default or the users home directory. blocks CWE-829
RHEL 9 (1 rule)
- V-258050 Executable search paths within the initialization files of all local interactive RHEL 9 users must only contain paths that resolve to the system default or the users home directory. blocks CWE-829
Windows 10 (1 rule)
- V-220737 Administrative accounts must not be used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. blocks CWE-829