CVE-2026-10239
Server-Side Request Forgery in JeecgBoot
Publication date: 2026-06-01
Last updated on: 2026-06-01
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jeecgboot | jeecgboot | to 3.9.2 (inc) |
| jeecgboot | jeecgboot | to 3.9.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Server-Side Request Forgery (SSRF) issue in JeecgBoot versions up to 3.9.2, specifically in the Word template processing feature. It occurs in the WordUtil.addImage function when processing Word templates via the /airag/word/edit endpoint.
An attacker can inject malicious HTTP URLs into the database through the main field of a Word template. Later, when the template is downloaded via the /airag/word/download endpoint, the server attempts to fetch images from these attacker-controlled URLs without proper host validation, only checking that the URL starts with http:// or https://.
This lack of validation allows attackers to make the server send HTTP requests to internal or restricted network resources, potentially scanning internal networks or accessing sensitive cloud metadata.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring and analyzing requests to the endpoints /airag/word/edit and /airag/word/download, which are involved in storing and triggering the SSRF exploit.
Specifically, detection involves identifying JSON payloads submitted to /airag/word/edit that contain Word template structures with image type cells referencing external HTTP or HTTPS URLs. These URLs may point to internal or sensitive network resources.
To detect exploitation attempts, you can use network monitoring tools or web server logs to look for unusual outbound HTTP requests initiated by the server when processing document downloads from /airag/word/download.
- Use curl or similar tools to simulate the attack payload and observe server behavior.
- Example command to check for suspicious POST requests with image URLs to /airag/word/edit in web server logs: grep -i '/airag/word/edit' /var/log/nginx/access.log | grep 'http://' or 'https://'
- Monitor outbound HTTP requests from the server to internal IP ranges or cloud metadata IPs during document generation.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoints /airag/word/edit and /airag/word/download to trusted users only.
Implement strict input validation on URLs submitted to the Word template image fields to ensure they do not point to internal or sensitive network resources.
Monitor and block outbound HTTP requests from the server to unauthorized or internal IP addresses to prevent SSRF exploitation.
Apply network-level controls such as firewall rules to limit server access to only necessary external resources.
Since a fix is planned for an upcoming release, plan to update JeecgBoot to the patched version as soon as it becomes available.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in JeecgBoot allows server-side request forgery (SSRF), which can enable attackers to access internal networks or sensitive cloud metadata by injecting malicious URLs. This type of unauthorized access could potentially lead to exposure or compromise of sensitive data.
Such unauthorized access and potential data exposure may impact compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.
However, the provided information does not explicitly detail the direct compliance impact or specific regulatory violations caused by this vulnerability.
How can this vulnerability impact me? :
This SSRF vulnerability can allow attackers to make the vulnerable server perform unauthorized HTTP requests to internal or protected network resources.
- Attackers may scan internal networks to discover sensitive services or infrastructure.
- Attackers could access sensitive cloud metadata services, potentially exposing credentials or configuration data.
- The vulnerability can be exploited remotely without user interaction.
- Exploitation could lead to further attacks or data breaches depending on the internal resources accessed.