Bricks vulnerabilities

Theme slug bricks · 10 known vulnerabilities · latest disclosed 2026-04-23 · WordPress.org page

Every listed vulnerability has a fix. Version 2.3 or later is not affected by any of them. If your site runs an older version, update it.

4 of 10 rated high or critical (CVSS 7 or more).

Known vulnerabilities in Bricks

SeverityAffected versionsFixed inCVEPublishedDetails
Medium 6.1<= 1.9.22.3CVE-2026-415542026-04-23Advisory
Medium 4.3<= 2.1.42.2CVE-2026-407232026-02-24Advisory
High 7.5<= 1.12.42.0CVE-2025-64952025-07-28Advisory
High 7.1<= 1.9.6.11.9.7CVE-2024-22972025-02-26Advisory
Medium 5.4<= 1.10.11.10.2CVE-2023-34102024-09-13Advisory
Medium 5.4<= 1.8.11.8.2CVE-2023-34092024-08-16Advisory
Medium 4.3<= 1.8.11.8.2CVE-2023-34082024-08-16Advisory
Critical 9.8<= 1.9.61.9.6.1CVE-2024-256002024-02-13Advisory
High 8.81.2 to 1.5.31.5.4CVE-2022-34012022-10-03Advisory
Medium 6.51.0 to 1.5.31.5.4CVE-2022-34002022-10-03Advisory

Check if a site is affected

Enter a site address to see which version of Bricks and other plugins it runs, and whether they match a known vulnerability.

Questions

Is the Bricks theme safe to use?

All 10 known issues are fixed in current versions (2.3 or later). Keeping it updated is what matters.

How do I check which version of Bricks my site runs?

In WordPress go to Appearance > Themes. From the outside, the free PluginPeek scan below reads the version from the site's public files.

How do I fix a vulnerable theme?

Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.

Check any WordPress site in one click while you browse: Add PluginPeek to Chrome