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

CVE-2026-7605

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-02
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 security flaw has been discovered in JeecgBoot up to 3.9.1. This vulnerability affects the function CommonController.uploadImgByHttp/HttpFileToMultipartFileUtil.httpFileToMultipartFile/HttpFileToMultipartFileUtil.downloadImageData of the file CommonController.java of the component uploadImgByHttpEndpoint. Performing a manipulation results in server-side request forgery. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. Upgrading the affected component is recommended. The vendor confirmed the issue and will provide a fix in the upcoming release.

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

JeecgBoot up to version 3.9.1 contains a Server-Side Request Forgery (SSRF) vulnerability in the CommonController.java file, specifically within the uploadImgByHttp endpoint and related utility functions (httpFileToMultipartFile and downloadImageData). The vulnerability allows remote attackers to make the server perform arbitrary requests to internal or external resources due to insufficient validation of user-supplied URLs in the file upload functionality.

MitigationUpgrade to the fixed version when released by the vendor. As an interim measure, implement URL allowlisting and block requests to internal/private network ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) in the affected upload functions until the vendor patch is available.

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 JeecgBoot version
    Locate the build configuration file (such as pom.xml or version properties) in the JeecgBoot deployment and determine the installed version number. Compare it against the affected range (up to and including version 3.9.1).
    Affected if The installed version is 3.9.1 or lower.
  2. Locate CommonController.java
    Search the application source code or decompiled classes for the file CommonController.java. This file typically resides in the controller or web layer of the Java application.
    Affected if The file CommonController.java exists in the codebase.
  3. Verify vulnerable endpoint exists
    Within CommonController.java, search for the method or endpoint named uploadImgByHttp. This endpoint handles file uploads from external URLs.
    Affected if The uploadImgByHttp method is present in the codebase.
  4. Confirm vulnerable utility functions
    Within the codebase, search for the functions httpFileToMultipartFile and downloadImageData. These functions are used by the uploadImgByHttp endpoint to fetch and process URLs.
    Affected if Both httpFileToMultipartFile and downloadImageData functions exist.
  5. Check endpoint accessibility
    Verify that the uploadImgByHttp endpoint is exposed and accessible. This typically requires network access to the application's web interface on the configured HTTP port.
    Affected if The endpoint is accessible over the network without authentication restrictions.

If JeecgBoot version 3.9.1 or lower is running with the CommonController.java file containing the uploadImgByHttp endpoint and its related utility functions exposed, the environment is vulnerable to CVE-2026-7605.

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

Upgrade to the fixed version when released by the vendor. As an interim measure, implement URL allowlisting and block requests to internal/private network ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) in the affected upload functions until the vendor patch is available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7605 — 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-7605 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