Is bricks (WordPress theme) vulnerable?

WordPress bricks has 6 known advisories in the phpwarden feed. Feed 2026.10.28.3, updated 2026-10-28.

6advisories
0critical
0on CISA KEV
1no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2022-3401The Bricks theme for WordPress is vulnerable to remote code execution due to the theme allowing site editors to include executable code blochigh8.8>=1.2 and <1.5.41.5.4
CVE-2022-3400The Bricks theme for WordPress is vulnerable to authorization bypass due to a missing capability check on the bricks_save_post AJAX action imedium6.5>=1.0 and <=1.5.3–
CVE-2024-2297The Bricks theme for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.9.6.1. This is due to insufficihigh7.1<1.9.71.9.7
CVE-2023-3410The Bricks theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘customTag' attribute in versions up to, and including, medium5.4<1.10.21.10.2
CVE-2023-3408The Bricks theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.8.1. This is due to missing omedium4.3<1.8.21.8.2
CVE-2023-3409The Bricks theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.8.1. This is due to missing omedium5.4<1.8.21.8.2

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.