dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-7065

HIGH · 7.3 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in BidingCC BuildingAI up to 26.0.1. Impacted is the function uploadRemoteFile of the file packages/core/src/modules/upload/services/file-storage.service.ts of the component Remote Upload API. The manipulation of the argument url leads to server-side request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in BidingCC BuildingAI's Remote Upload API. The uploadRemoteFile function in file-storage.service.ts accepts user-controlled URL input without proper validation, allowing attackers to make the server request arbitrary URLs. This could enable access to internal services, cloud metadata endpoints, or port scanning of internal infrastructure.

MitigationImplement strict URL validation with allowlist filtering, block requests to internal/private IP ranges (127.0.0.1, 10.x, 192.168.x, etc.), and disable the remote upload feature until a vendor patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm BidingCC BuildingAI installation
    Identify the application name and verify it is BidingCC BuildingAI by checking the product documentation, installed software list, or application banner
    Affected if The installed product is not BidingCC BuildingAI (not affected)
  2. Check Remote Upload API availability
    Determine if the Remote Upload API endpoint is accessible or enabled in the application configuration. Look for API routes such as /api/upload/remote or similar endpoints in the codebase
    Affected if The Remote Upload API is exposed and accessible to users
  3. Identify installed version
    Locate the version information for BuildingAI installation - check package.json, configuration files, or the application's 'about' or version endpoint if available. Compare the installed version against any vendor release notes
    Affected if The installed version is unpatched and the vendor has released a fix for CVE-2026-7065
  4. Inspect file-storage.service.ts configuration
    Locate the file-storage.service.ts file in the application source or deployed code. Examine the uploadRemoteFile function for URL validation logic. Check if user-controlled URL parameters are validated before being used in server requests
    Affected if The uploadRemoteFile function lacks proper URL validation and accepts arbitrary user-provided URLs
  5. Verify URL allowlist implementation
    Review the application's URL validation logic to determine if an allowlist filter is implemented for remote upload URLs. Check if internal/private IP ranges (127.0.0.1, 10.x, 192.168.x, etc.) and cloud metadata endpoints are explicitly blocked
    Affected if No URL allowlist exists or internal IP ranges are not blocked

The environment is affected if BidingCC BuildingAI is installed with the Remote Upload API enabled, the version is unpatched, and the uploadRemoteFile function lacks proper URL validation to prevent requests to internal/private addresses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation with allowlist filtering, block requests to internal/private IP ranges (127.0.0.1, 10.x, 192.168.x, etc.), and disable the remote upload feature until a vendor patch is released.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7065 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data