# CVE-2022-3401: Code injection in Bricks

> Authenticated attackers with minimal permissions can inject executable code blocks to achieve remote code execution on sites using the Bricks theme.

- **Severity:** High 8.8 (`CVSS:3.1/A:H/I:H/C:H/S:U/UI:N/PR:L/AC:L/AV:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2022
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-r2w6-f5cp-rrh7

## What is CVE-2022-3401?

CVE-2022-3401 is a high-severity code injection vulnerability in Bricks, published on 28 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2022-3401?

It affects 1 product.


Products: Bricksbuilder Bricks.

## How do I fix CVE-2022-3401?

No fix has been published for CVE-2022-3401 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-3401 being exploited?

There is no known exploitation of CVE-2022-3401 in the wild and no public exploit code.

## Other vulnerabilities in Bricks

- [CVE-2024-2297](https://insights.sbomify.com/CVE-2024-2297/): Bricksbuilder <= 1.9.6.1 - Authenticated (Contributor+) Privilege Escalation via create_autosave (high 7.1)
- [CVE-2022-3400](https://insights.sbomify.com/CVE-2022-3400/): Missing authorization in Bricks (medium 6.5)
- [CVE-2023-3410](https://insights.sbomify.com/CVE-2023-3410/): Bricks <= 1.10.1 - Authenticated (Bricks Page Builder Access+) Stored Cross-Site Scripting (medium 5.4)
- [CVE-2023-3409](https://insights.sbomify.com/CVE-2023-3409/): Bricks <= 1.8.1 - Cross-Site Request Forgery via reset_settings (medium 5.4)
- [CVE-2023-3408](https://insights.sbomify.com/CVE-2023-3408/): Bricks <= 1.8.1 - Cross-Site Request Forgery via save_settings (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3401 and fix it if it is affected.

What it is: CVE-2022-3401 is a high-severity code injection vulnerability in Bricks, published on 28 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3401 in the wild and no public exploit code.

Affected product: Bricks. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3401/ (Markdown: https://insights.sbomify.com/CVE-2022-3401/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3401
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3401
- OSV: https://osv.dev/vulnerability/CVE-2022-3401

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3401/
Summaries are generated and may contain mistakes; the official description above is the record.