CVE-2025-60541: prompt-optimizer · n/a
Affects prompt-optimizerSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHublinshenkx/prompt-optimizerpkg:github/linshenkx/prompt-optimizerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since no official patches are currently available, European organizations should implement immediate compensating controls. First, restrict external access to the /api/proxy/ endpoint using network firewalls, web application firewalls (WAFs), or API gateways to ensure only trusted internal clients can reach it. Implement strict input validation and URL allowlisting on the proxy API to prevent arbitrary request forwarding. Employ network segmentation and zero-trust principles to limit the exposure of sensitive internal resources, ensuring that even if SSRF occurs, the attacker’s ability to reach critical assets is minimized. Monitor logs and network traffic for unusual outbound requests originating from the prompt-optimizer service. Consider deploying runtime application self-protection (RASP) solutions to detect and block SSRF attempts. Finally, maintain close communication with the vendor for timely patch releases and apply updates as soon as they become available.
Description
A Server-Side Request Forgery (SSRF) in the /api/proxy/ component of linshenkx prompt-optimizer v1.3.0 to v1.4.2 allows attackers to scan internal resources via a crafted request.