CVE-2025-0188 json
SSRF in gaizhenbiao/chuanhuchatgpt
published last yr. modified 4mo ago also PYSEC-2025-98 , EUVD-2025-6818
- cvss
- 6.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
A Server-Side Request Forgery (SSRF) vulnerability was discovered in gaizhenbiao/chuanhuchatgpt version 20240914. The vulnerability allows an attacker to construct a response link by saving the response in a folder named after the SHA-1 hash of the target URL. This enables the attacker to access the response directly, potentially leading to unauthorized access to internal systems, data theft, service disruption, or further attacks such as port scanning and accessing metadata endpoints.
Is CVE-2025-0188 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- huntr.com https://huntr.com/bounties/879d2470-eca5-49c0-b3d1-57469cfff412 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | chuanhuchatgpt | <=20240914 |
no fix listed |
Affected products
- gaizhenbiao gaizhenbiao/chuanhuchatgpt
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
huntr.com
/bounties/879d2470-eca5-49c0-b3d1-57469cfff412
exploit, third-party-advisory, evidence
Sources
- CVE List CVE-2025-0188
- NVD CVE-2025-0188
- OSV PYSEC-2025-98
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.