Cross-user content modification via unchecked postId
Published Jun 22, 2024 · Updated Apr 8, 2026
Authorization bypass in Bricks Builder 1.9.8 and earlier allows remote authenticated users to modify posts owned by other users. The builder save path trusts the user-controlled postId key without checking whether the contributor owns the selected post, so Bricks writes generated content to another user's post. Reachability requires contributor-level builder access enabled by an administrator; the flaw changes generated content but does not grant executable-code editing.
Summary
What happened
Authorization bypass in Bricks Builder 1.9.8 and earlier allows remote authenticated users to modify posts owned by other users. The builder save path trusts the user-controlled postId key without checking whether the contributor owns the selected post, so Bricks writes generated content to another user's post. Reachability requires contributor-level builder access enabled by an administrator; the flaw changes generated content but does not grant executable-code editing.
The record
- CVE
- CVE-2024-4874
- Published
- Jun 22, 2024
- Updated
- Apr 8, 2026
- Vendor
- Bricks Builder
- Product
- Bricks Builder
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 22, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record 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=0 <=1.9.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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