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

CVE-2026-3683

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 was detected in bufanyun HotGo up to 2.0. This issue affects the function ImageTransferStorage of the file /server/internal/logic/common/upload.go of the component Endpoint. The manipulation results in server-side request forgery. The attack may be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

The ImageTransferStorage function in /server/internal/logic/common/upload.go of HotGo up to v2.0 contains a Server-Side Request Forgery (SSRF) vulnerability in the upload endpoint. An attacker can manipulate the function to make the server fetch files from arbitrary URLs, potentially accessing internal services, cloud metadata endpoints, or internal network resources.

MitigationImplement strict URL validation and allowlist-based filtering for the ImageTransferStorage function to restrict fetches to approved domains or internal paths only. If no vendor patch is available, consider disabling the affected functionality or deploying a WAF with SSRF detection rules.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify HotGo installation and version
    Locate the HotGo application binary or source code. If source is available, check version in go.mod, a VERSION file, or git tags. If binary, run: ./hotgo --version or ./hotgo -v
    Affected if Version is v2.0 or lower (including unversioned builds)
  2. Locate the vulnerable upload.go file
    Search for the file /server/internal/logic/common/upload.go in the HotGo source code. If only a binary is available, use strings or a hex editor to search for 'ImageTransferStorage' within the binary.
    Affected if The file exists and contains the ImageTransferStorage function
  3. Verify the ImageTransferStorage function is present
    Grep for 'func ImageTransferStorage' or 'ImageTransferStorage' in the upload.go file. Alternatively, search the binary for this function name.
    Affected if The function is found in the codebase or binary
  4. Confirm upload endpoint exposure
    Identify if the upload functionality is exposed via HTTP/HTTPS. Check router configuration for upload routes (commonly /upload, /api/upload, or similar). Test accessing these endpoints if you have access: curl -I https://yourserver/upload
    Affected if The upload endpoint is accessible via network (HTTP/HTTPS exposed)
  5. Inspect URL handling in ImageTransferStorage
    Review the source code of ImageTransferStorage to check if user-controlled URL input is passed to HTTP client calls without strict validation. Look for http.Get, http.Client, or similar without allowlist filtering.
    Affected if The function accepts URLs from user input and makes outbound requests without validated allowlists

You are affected if HotGo v2.0 or lower is running with the upload endpoint exposed and the ImageTransferStorage function accepts unvalidated URLs from user input.

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 and allowlist-based filtering for the ImageTransferStorage function to restrict fetches to approved domains or internal paths only. If no vendor patch is available, consider disabling the affected functionality or deploying a WAF with SSRF detection rules.

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-3683 — 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-3683 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