CVE-2024-1311
Brizy ≤ 2.4.41
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-1311 is a high-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Brizy Brizy. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 26% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — 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.
The Brizy – Page Builder plugin for WordPress contains an arbitrary file upload vulnerability stemming from missing file type validation in the storeImages function within its archiver component. The flaw affects all versions through 2.4.40 and is tracked under CWE-434, carrying a CVSS 3.1 score of 8.8.
Authenticated users with contributor privileges or greater can exploit the issue over the network to upload arbitrary files to the server, which may enable remote code execution and full compromise of the affected site.
The issue was resolved in version 2.4.41 through an update to the archiver.php file that restores proper validation, as reflected in the official WordPress plugin changeset and corroborated by the Wordfence threat intelligence entry.
EPSS scores have remained essentially flat near 0.1 with only a negligible peak-to-current difference, providing no indication of rising exploitation interest.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-17071
Vulnerability Data
The Brizy – Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the storeImages function in all versions up to, and including, 2.4.40. This makes it possible for authenticated attackers, with…
more
contributor access or above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Mitigating Controls (NIST 800-53 r5) AI
Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.
Least functionality restricts the file types and automatic processing capabilities the system will accept.
Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.
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.
Hardened configuration baselines can enforce allowed file types and processing rules.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
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.