Incident Score: Analysis & Impact (WP-BRI1791865446)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Bricks Builder's Vulnerability and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Bricks Builder Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Bricks Builder breach identified under incident ID WP-BRI1791865446.
The analysis begins with a detailed overview of Bricks Builder's information like the linkedin page: https://www.linkedin.com/company/bricks-builder, the number of followers: 930, the industry type: Software Development and the number of employees: 7 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 750 and after the incident was 747 with a difference of -3 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Bricks Builder and their customers.
On 07 October 2026, Bricksforge disclosed Zero-Day Exploit issues under the banner "Critical Zero-Day Exploit Targets Bricksforge WordPress Plugin (CVE-2026-85097)".
Attackers are actively exploiting a severe vulnerability in the Bricksforge WordPress plugin, tracked as CVE-2026-85097, allowing unauthenticated remote code execution (RCE).
The disruption is felt across the environment, affecting WordPress websites using Bricksforge plugin (versions ≤ 3.1.8.9), and exposing Sensitive data exfiltration possible.
In response, moved swiftly to contain the threat with measures like Update to Bricksforge version 3.1.8.10 or 4.0.1, log review, directory inspection, and began remediation that includes Patch release (3.1.8.10), security fix for Pro Forms (4.0.1), while recovery efforts such as Compromise review for exposed installations continue.
The case underscores how Ongoing (exploitation attempts detected, mitigation released), teams are taking away lessons such as Risks of unsafe file handling in WordPress plugins, where upload features can be weaponized for RCE. Importance of revalidating user-supplied file details and monitoring for mixed file extensions, and recommending next steps like Update immediately to Bricksforge version 3.1.8.10 or 4.0.1, Review logs for suspicious `temporaryFileUploads` submissions and Inspect upload directories for unexpected PHP files, with advisories going out to stakeholders covering Administrators urged to update immediately and review for compromise.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with high confidence (95%), supported by evidence indicating attackers are actively exploiting a severe vulnerability in the Bricksforge WordPress plugin and Exploitation of Remote Services (T1210) with high confidence (90%), supported by evidence indicating allowing unauthenticated remote code execution (RCE) via file upload functionality. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: PowerShell (T1059.001) with moderate to high confidence (70%), supported by evidence indicating execute arbitrary PHP code on affected websites, Command and Scripting Interpreter: Python (T1059.006) with moderate confidence (60%), supported by evidence indicating pHP code execution implies scripting interpreter abuse, and Exploitation for Client Execution (T1203) with moderate to high confidence (85%), supported by evidence indicating triggering code execution when the server processes the malicious file. Under the Persistence tactic, the analysis identified Server Software Component: Web Shell (T1505.003) with moderate to high confidence (80%), supported by evidence indicating deploy web shells...or maintain persistent access. Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (70%), supported by evidence indicating unauthenticated RCE implies potential privilege escalation. Under the Defense Evasion tactic, the analysis identified Masquerading: Rename System Utilities (T1036.003) with moderate to high confidence (85%), supported by evidence indicating uploading a file disguised as an image (e.g., a GIF with embedded PHP code), Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (80%), supported by evidence indicating 95% of requests used .gif or .png extensions paired with PHP destination URLs, and Deobfuscate/Decode Files or Information (T1140) with moderate to high confidence (70%), supported by evidence indicating attackers tested mixed capitalization, encoded filenames. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with moderate confidence (60%), supported by evidence indicating arbitrary PHP code execution may access stored credentials. Under the Discovery tactic, the analysis identified File and Directory Discovery (T1083) with moderate to high confidence (70%), supported by evidence indicating inspect upload directories for unexpected PHP files. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating exfiltrate sensitive data. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (75%), supported by evidence indicating data exfiltration possible via arbitrary PHP code execution. Under the Impact tactic, the analysis identified Defacement: Internal Defacement (T1491.001) with moderate to high confidence (80%), supported by evidence indicating alter website content and Data Manipulation: Stored Data Manipulation (T1565.001) with moderate to high confidence (70%), supported by evidence indicating arbitrary PHP code execution enables data manipulation. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Bricks Builder Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/bricks-builder/incident/WP-BRI1791865446
- Bricks Builder CyberSecurity Rating page: https://www.rankiteo.com/company/bricks-builder
- Bricks Builder Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/wp-bri1791865446-bricksforge-bricks-builder-vulnerability-october-2026/
- Bricks Builder CyberSecurity Score History: https://www.rankiteo.com/company/bricks-builder/history
- Bricks Builder CyberSecurity Incident Source: https://cybersecuritynews.com/wordpress-plugin-vulnerability-exploited/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf