WordPress security by component

Bricks Builder

Theme description

Bricks Builder is a WordPress component with 11 published CVE records in this archive. The latest tracked vulnerability was published Jun 17, 2026; the highest CVE/CNA score is 10.

Theme slug: bricks

Latest vulnerability

CVE-2026-40723: Bricks Builder: A security weakness

Bricks Builder is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 2.1.4.

PublishedJun 17, 2026

Known safe version2.2

		Safe version
Jun 17, 2026	CVE-2026-40723 Bricks Builder: A security weakness Bricks Builder is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 2.1.4.	2.2	CVE4.3 NVDPending
May 07, 2026	CVE-2026-41554 Bricks Builder: Cross-site scripting Bricks Builder is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is 1.9.2 through 2.2.	2.3	CVE7.1 NVDPending
Jul 29, 2025	CVE-2025-6495 Bricks: SQL injection Bricks is affected by SQL injection. The vulnerable path is reachable without authentication. A successful request can alter database queries and expose or modify WordPress data.	See mitigation notes	CVE7.5 NVDPending
Feb 27, 2025	CVE-2024-2297 Bricks: Privilege escalation or authentication bypass Bricks is affected by privilege escalation or authentication bypass. Exploitation requires at least contributor-level access. A successful request can grant permissions or access that the caller should not possess.	See mitigation notes	CVE7.1 NVD8.8
Sep 14, 2024	CVE-2023-3410 Bricks: Cross-site scripting Bricks is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.	See mitigation notes	CVE5.4 NVD5.4
Aug 17, 2024	CVE-2023-3409 Bricks: Cross-site request forgery Bricks is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.	See mitigation notes	CVE5.4 NVD4.3
Aug 17, 2024	CVE-2023-3408 Bricks: Cross-site request forgery Bricks is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.	See mitigation notes	CVE4.3 NVDPending
Jun 22, 2024	CVE-2024-4874 Bricks Builder: A security weakness Bricks Builder is affected by a security weakness. Exploitation requires at least contributor-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.	See mitigation notes	CVE4.3 NVD4.3
Jun 04, 2024	CVE-2024-25600 Bricks Builder: Code execution Bricks Builder is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.	See mitigation notes	CVE10.0 NVDPending
Oct 28, 2022	CVE-2022-3401 Bricks: Code execution Bricks is affected by code execution. Exploitation requires an authenticated WordPress account. Successful exploitation can run attacker-controlled code in the WordPress hosting account.	See mitigation notes	CVE8.8 NVD8.8
Oct 28, 2022	CVE-2022-3400 Bricks: A security weakness Bricks is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.	See mitigation notes	CVE6.5 NVD6.5