Subscriber-level code execution via executable content blocks
Published Oct 28, 2022 · Updated Jan 31, 2025
Code injection in Bricks Builder 1.2 through 1.5.3 allows remote authenticated users to execute arbitrary PHP through page content. The Code element executes PHP blocks, while insufficient capability checks let subscriber-level accounts modify pages, posts, or templates and insert executable content. Exploitation requires an authenticated subscriber and the separate content-authorization weakness; successful execution runs attacker-supplied PHP in the website context.
Summary
What happened
Code injection in Bricks Builder 1.2 through 1.5.3 allows remote authenticated users to execute arbitrary PHP through page content. The Code element executes PHP blocks, while insufficient capability checks let subscriber-level accounts modify pages, posts, or templates and insert executable content. Exploitation requires an authenticated subscriber and the separate content-authorization weakness; successful execution runs attacker-supplied PHP in the website context.
The record
- CVE
- CVE-2022-3401
- Published
- Oct 28, 2022
- Updated
- Jan 31, 2025
- Vendor
- Bricks Builder
- Product
- Bricks Builder
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 28, 2022CVE publishedPublication date reported by the CVE source.
- Jan 31, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2 <=1.5.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo