CVE-2024-25600: WordPress Bricks Theme <= 1.9.6 - Unauthenticated Remote Code Execution (RCE) vulnerability
Noroxi assessment
Priority: This week (action score 67/100)
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 91% (FIRST EPSS); higher than 99.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Codeer Limited Bricks Builder 1.9.6.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Don’t wait for the next maintenance window. Upgrade to Codeer Limited Bricks Builder 1.9.6.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper Control of Generation of Code ('Code Injection') vulnerability in Codeer Limited Bricks Builder allows Code Injection.This issue affects Bricks Builder: from n/a through 1.9.6.
- Published
- Jun 4, 2024
- Updated
- Jun 17, 2026
- EPSS
- 91.0% · 99th percentile
- CWE
- CWE-94
Report tools
Action score
67
This week
Don’t wait for the next maintenance window.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 27 / 30 · 91.0%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Patchstack
- 10.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Is Bricks on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| bricksbuilder | bricks | cpe:2.3:a:bricksbuilder:bricks |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Patchstack). Independent of NVD's CPE analysis and usually ahead of it.
Codeer Limited Bricks Builder
- n/a and later · up to and including 1.9.6affectedfixed in 1.9.6.1
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Codeer Limited Bricks Builder | 1.9.6.1 | Vendor (CNA) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Exploit-DB entry ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×20
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2026-07-07 |
| Metasploit module | exploit/multi/http/wp_bricks_builder_rceUnauthenticated RCE in Bricks Builder Themeexploit | 2024-02-19 |
| Nuclei detection template | Nuclei template CVE-2024-25600 | — |
| Proof-of-concept repository on GitHub | stars:183 | 2024-02-20 |
| Proof-of-concept repository on GitHub | stars:31 | 2024-02-21 |
| Proof-of-concept repository on GitHub | stars:8 | 2024-02-22 |
| Proof-of-concept repository on GitHub | stars:1 | 2024-04-20 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-05-17 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-06-06 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-06-06 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-07-30 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-08-20 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-106 d
- First PoC-105 d
- Published
- TodayNov 4, 2026+883 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0605 · Jun 7, 2024(WordPress Eklenti Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
- github.com/K3ysTr0K3R/CVE-2024-25600-EXPLOIT
- patchstack.com/articles/critical-rce-patched-in-bricks-builder-theme?_s_id=cve
- patchstack.com/database/vulnerability/bricks/wordpress-bricks-theme-1-9-6-unauthenticated-remote-code-execution-rce-vulnerability?_s_id=cve
- snicco.io/vulnerability-disclosure/bricks/unauthenticated-rce-in-bricks-1-9-6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.