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

CVE-2026-7604

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 vulnerability was identified in JeecgBoot up to 3.9.1. This affects the function OpenApiController.add/OpenApiController.call of the file OpenApiController.java of the component OpenApi Service. Such manipulation of the argument originUrl database leads to server-side request forgery. It is possible to launch the attack remotely. The exploit is publicly available and might be used. It is suggested to upgrade the affected component. 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 OpenApi Service component. The OpenApiController.add and OpenApiController.call functions fail to properly validate the originUrl parameter stored in the database, allowing attackers to manipulate the server into making arbitrary HTTP requests to internal or external resources.

MitigationUpgrade to the fixed JeecgBoot version when the vendor releases the patch. As a temporary control, implement network segmentation and restrict outbound access from the server to prevent exploitation of internal services.

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 installation and version
    Locate the JeecgBoot application files (JAR, WAR, or source code). Check for version information in pom.xml, application.yml/properties, or version manifest files. Compare the found version to the affected range (up to and including 3.9.1).
    Affected if JeecgBoot version is 3.9.1 or lower
  2. Verify OpenApi component is enabled
    Search for OpenApiController.class or OpenApiController.java in the deployed application files. Check if the OpenApi module is included in the build configuration or deployed components.
    Affected if OpenApiController class exists and is deployed in the application
  3. Confirm OpenApi endpoint accessibility
    Check application routing configuration (such as Spring MVC mappings) for /openapi/add and /openapi/call endpoints. Attempt a HEAD request to these paths if you have access, or review the application's exposed REST endpoints list.
    Affected if The /openapi/add or /openapi/call endpoints are accessible without authentication or with attacker-reachable authentication
  4. Inspect OpenApi database records for originUrl
    Query the database table that stores OpenApi configurations (commonly named api_data, open_api, or similar). Look for records with an originUrl field that could contain attacker-controlled URLs.
    Affected if The database contains OpenApi records with an originUrl field that is not validated or is user-modifiable

You are affected if you run JeecgBoot version 3.9.1 or earlier AND the OpenApi component with its /openapi endpoints is enabled and accessible, allowing unvalidated originUrl values to be stored and later used in server requests.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the fixed JeecgBoot version when the vendor releases the patch. As a temporary control, implement network segmentation and restrict outbound access from the server to prevent exploitation of internal services.

Recommended fix Moderate confidence

Version beyond 3.9.1 (await official fixed release - check JeecgBoot GitHub releases)

  1. 1. Identify the current JeecgBoot version in use by checking the project's pom.xml or build configuration
  2. 2. Check the official JeecgBoot GitHub repository (github.com/jeecgboot/JeecgBoot) or release notes for the fixed version that addresses CVE-2026-7604
  3. 3. Review the release notes between version 3.9.1 and the fixed version for any breaking changes or migration requirements
  4. 4. Update the version in pom.xml or build configuration to the fixed release version
  5. 5. Run the application's test suite to verify functionality after upgrade
  6. 6. Verify that the OpenApiService endpoint no longer accepts arbitrary URLs via the originUrl parameter
Caveat Review release notes for the fixed version; specific breaking changes for OpenApiService not detailed in available materials

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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