CVE-2022-3401

Bricks 1.2 - 1.5.3 - Remote Code Execution

2022-10-03 00:00
Anonymous

Strategic Overview

Status
Patched in 1.5.4
Affected Theme
Bricks
Affected Version
1.2 – 1.5.3
CVSS
8.8High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2022-3401
View all Bricks vulnerabilities

At a glance

CVE-2022-3401 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Bricks WordPress theme, affecting versions 1.2 – 1.5.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.5.4; sites on affected versions should update now. Disclosed October 2022.

Vulnerability Overview

The Bricks theme for WordPress is vulnerable to remote code execution due to the theme allowing site editors to include executable code blocks in website content in versions 1.2 to 1.5.3. This, combined with the missing authorization vulnerability (CVE-2022-3400), makes it possible for authenticated attackers with minimal permissions, such as a subscriber, can edit any page, post, or template on the vulnerable WordPress website and inject a code execution block that can be used to achieve remote code execution.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Bricks 1.2 – 1.5.3 takes a caller who can reach the endpoint. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Bricks the fix is 1.5.4: builds 1.2 – 1.5.3 are affected, anything from 1.5.4 onward is not.

Remediation

Update to version 1.5.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Bricks: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Bricks 1.5.4 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-3401https://www.wordfence.com/threat-intel/vulnerabilities/id/2471d06b-7d9a-41b9-b38c-3f40322d8a5bhttps://nvd.nist.gov/vuln/detail/CVE-2022-3401

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C