Authenticated file read and SSRF via resource URI
Published May 26, 2025 · Updated May 28, 2025
Server-side request forgery in ThinkGem JeeSite 5.11.0 through 5.11.1 allows remote authenticated users to read files or request URLs. The cms/template/form handler passes its name parameter through fileTempleteService.getFileTemplete to ResourceUtils.getResource without scheme validation. A valid JeeSite session is required; file, HTTP, and FTP resource schemes expose local files and network-reachable services to the server's access.
Summary
What happened
Server-side request forgery in ThinkGem JeeSite 5.11.0 through 5.11.1 allows remote authenticated users to read files or request URLs. The cms/template/form handler passes its name parameter through fileTempleteService.getFileTemplete to ResourceUtils.getResource without scheme validation. A valid JeeSite session is required; file, HTTP, and FTP resource schemes expose local files and network-reachable services to the server's access.
The record
- CVE
- CVE-2025-5186
- Published
- May 26, 2025
- Updated
- May 28, 2025
- Vendor
- ThinkGem
- Product
- JeeSite
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2025CVE publishedPublication date reported by the CVE source.
- May 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.11.0
- Affected versionversion=5.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- JeeSite 5 SSRF and arbitrary file-read proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo