CVE-2024-27565: ChatGPT-wechat-personal · Server-Side Request Forgery (SSRF)
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Mar 2024
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 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-27565 effectively, organizations should: 1) Conduct a thorough code review and audit of the ChatGPT-wechat-personal deployment to identify and isolate the vulnerable weixin.php component. 2) Implement strict input validation and sanitization to ensure that user-supplied URLs or parameters cannot be manipulated to trigger arbitrary requests. 3) Employ allowlisting for outbound requests from the application, restricting destinations to known safe endpoints only. 4) Use network segmentation and firewall rules to limit the application server's ability to reach internal services or sensitive infrastructure. 5) Monitor outbound traffic from the application for unusual or unexpected requests that could indicate exploitation attempts. 6) If possible, update or patch the software once a fix becomes available from the maintainers. 7) Consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities to block malicious request patterns. 8) Educate development teams on secure coding practices to prevent SSRF and similar vulnerabilities in future releases. 9) Maintain an incident response plan to quickly address any detected exploitation. These steps go beyond generic advice by focusing on network-level controls and proactive monitoring tailored to SSRF risks.
Description
A Server-Side Request Forgery (SSRF) in weixin.php of ChatGPT-wechat-personal commit a0857f6 allows attackers to force the application to make arbitrary requests.