CVE-2024-2297 Vulnerability Analysis & Exploit Details

CVE-2024-2297
Vulnerability Scoring

7.1
/10
Very High Risk

Highly exploitable, CVE-2024-2297 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2024-2297 Details

Status: Analyzed

Last updated: 🕢 11 Mar 2025, 19:39 UTC
Originally published on: 🕕 27 Feb 2025, 06:15 UTC

Time between publication and last update: 12 days

CVSS Release: version 3

CVSS3 Source

security@wordfence.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

CVE-2024-2297 Vulnerability Summary

CVE-2024-2297: The Bricks theme for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.9.6.1. This is due to insufficient validation checks placed on the create_autosave AJAX function. This makes it possible for authenticated attackers, with contributor-level access and above, to execute arbitrary PHP code with elevated (administrator-level) privileges. NOTE: Successful exploitation requires (1) the Bricks Builder to be enabled for posts (2) Builder access to be enabled for contributor-level users, and (3) "Code Execution" to be enabled for administrator-level users within the theme's settings.

Assessing the Risk of CVE-2024-2297

Access Complexity Graph

The exploitability of CVE-2024-2297 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-2297

This vulnerability, CVE-2024-2297, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-2297, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-2297, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2024-2297 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2024-2297 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2024-2297 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.05% (probability of exploit)

EPSS Percentile: 22.18% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 77.82% of others.

CVE-2024-2297 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:bricksbuilder:bricks:-:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:-:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.2.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.2.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.2.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.2.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.2.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.2.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.3.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.3.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.3.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.3.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.3.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.3.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.3.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.3.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.3.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.3.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.3.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.3.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.3.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.3.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.4.0.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.4.0.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.4.0.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.4.0.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.4.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.4.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.5.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.5.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.5.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.5.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.5.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.5.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.5.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.5.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.5.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.5.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.5.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.5.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.5.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.5.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.6.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.6.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.6.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.6.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.7.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.7.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.7.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.7.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.7.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.7.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.8.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.8.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.8.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.8.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.8.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.8.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.8.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.8.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.8.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.8.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.8.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.8.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9.1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9.1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:bricksbuilder:bricks:1.9.6.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:bricksbuilder:bricks:1.9.6.1:*:*:*:*:wordpress:*:*

Protect Your Infrastructure against CVE-2024-2297: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2855 – A vulnerability, which was classified as problematic, has been found in elunez eladmin up to 2.7. Affected by this issue is the function checkFile ...
  • CVE-2025-29072 – An integer overflow in Nethermind Juno before v.12.05 within the Sierra bytecode decompression logic within the "cairo-lang-starknet-classes" libra...
  • CVE-2025-28138 – TOTOLINK A800R V4.1.2cu.5137_B20200730 contains a remote command execution vulnerability in the setNoticeCfg function through the NoticeUrl parameter.
  • CVE-2025-28135 – TOTOLINK A810R V4.1.2cu.5182_B20201026 was found to contain a buffer overflow vulnerability in downloadFile.cgi.
  • CVE-2025-26909 – Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in John Darrel Hide My WP Gho...