BidingCC BuildingAI SSRF Vulnerability (CVE-2026-7065)
A server-side request forgery (SSRF) vulnerability exists in BidingCC BuildingAI up to version 26.0.1, allowing remote attackers to manipulate the `url` argument in the `uploadRemoteFile` function of `file-storage.service.ts` to conduct SSRF attacks.
BidingCC BuildingAI, up to version 26.0.1, is vulnerable to a server-side request forgery (SSRF) attack. The vulnerability resides within the uploadRemoteFile function located in packages/core/src/modules/upload/services/file-storage.service.ts. An attacker can remotely manipulate the url argument passed to this function to force the server to make requests to arbitrary internal or external resources. This vulnerability has been publicly disclosed and is considered exploitable. The vendor was notified of the issue, but has not responded. Successful exploitation can lead to information disclosure, internal service compromise, or other malicious activities.
Attack Chain
- Attacker identifies a BidingCC BuildingAI instance running a vulnerable version (<= 26.0.1).
- Attacker crafts a malicious URL containing the address of an internal resource or external server.
- Attacker calls the
uploadRemoteFileAPI endpoint, providing the crafted URL as theurlargument. - The
uploadRemoteFilefunction, without proper validation, uses the provided URL to initiate a request. - The BuildingAI server makes an HTTP request to the attacker-specified URL.
- If the URL points to an internal resource, the server retrieves sensitive data from that resource.
- If the URL points to an external server controlled by the attacker, the server may leak internal information (e.g., internal IP addresses) or be used for further attacks.
- The attacker receives the response from the manipulated request, achieving information disclosure or a foothold for further exploitation.
Impact
Successful exploitation of the SSRF vulnerability (CVE-2026-7065) in BidingCC BuildingAI can lead to the exposure of sensitive internal information, such as configuration files, internal service endpoints, and potentially database credentials. This information can be leveraged to further compromise the BuildingAI instance or other internal systems. The impact is significant due to the potential for lateral movement and privilege escalation within the affected organization’s infrastructure. The lack of vendor response exacerbates the risk.
Recommendation
- Deploy the Sigma rule provided below to detect exploitation attempts against the
uploadRemoteFileendpoint (Log source: webserver). - Implement strict input validation and sanitization on the
urlparameter of theuploadRemoteFilefunction to prevent arbitrary URL requests (CVE-2026-7065). - Consider restricting outbound network access from the BuildingAI server to only necessary resources to limit the impact of successful SSRF attacks.
- Monitor web server logs for unusual requests originating from the BuildingAI server to detect potential SSRF activity.
Detection coverage 2
Detect BuildingAI SSRF Attempt via URL Parameter
highDetects attempts to exploit the SSRF vulnerability in BuildingAI by monitoring requests to the uploadRemoteFile endpoint with suspicious URL parameters.
Detect BuildingAI SSRF Attempt via POST Request
highDetects attempts to exploit the SSRF vulnerability in BuildingAI by monitoring POST requests to the uploadRemoteFile endpoint with suspicious URL parameters in the request body.
Detection queries are kept inside the platform. Get full rules →