Security Resilience

CVE-2024-10960

Brizy ≤ 2.6.5

Published
12 February 2025
Modified
20 February 2025
Patch / advisory
CVSS Score v3.1 9.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0091 59th percentile
Risk Priority 74 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-10960 is a critical-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Brizy Brizy. Its CVSS base score is 9.9 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 41% 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.

CVE-2024-10960 is an arbitrary file upload vulnerability in the Brizy – Page Builder plugin for WordPress, stemming from missing file type validation in the 'storeUploads' function. It affects all versions up to and including 2.6.4. The flaw, associated with CWE-434 (Unrestricted Upload of File with Dangerous Type), has a CVSS v3.1 base score of 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), indicating critical severity due to its network accessibility, low complexity, and potential for high-impact confidentiality, integrity, and availability effects.

Authenticated attackers with Contributor-level access or higher can exploit this vulnerability to upload arbitrary files to the affected WordPress site's server. Successful exploitation may enable remote code execution, allowing attackers to execute malicious code in the context of the web server process.

References point to mitigation via an update to Brizy version 2.6.5, as evidenced by the WordPress plugin trac changeset addressing the issue in the editor/zip/archiver.php file. The Wordfence threat intelligence advisory provides further details on the vulnerability. Security practitioners should urge site owners to update the plugin immediately and review access controls for Contributor roles.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Brizy – Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'storeUploads' function in all versions up to, and including, 2.6.4. This makes it possible for authenticated attackers, with…

more

Contributor-level access and 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

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
T1011.001 Exfiltration Over Bluetooth Exfiltration
Adversaries may attempt to exfiltrate data over Bluetooth rather than the command and control channel.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-1311Same product: Brizy Brizy
CVE-2024-3242Same product: Brizy Brizy
CVE-2024-1165Same product: Brizy Brizy
CVE-2024-3667Same product: Brizy Brizy
CVE-2024-1291Same product: Brizy Brizy
CVE-2024-2087Same product: Brizy Brizy
CVE-2025-32198Same product: Brizy Brizy
CVE-2024-1296Same product: Brizy Brizy
CVE-2025-22763Same product: Brizy Brizy
CVE-2024-1164Same product: Brizy Brizy

Affected Assets

brizy
brizy
≤ 2.6.5

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

SC-18 Mobile Code partial match

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.

PR.PS-01 partial match
blocks

Hardened configuration baselines can enforce allowed file types and processing rules.

PR.PS-05 partial match
blocks

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

PR.PS-06 partial match
blocks

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.

References