CVE-2024-53507: siyuan · n/a
Affects siyuanSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% 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 29 Nov 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther 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
To mitigate CVE-2024-53507, organizations should immediately restrict external access to the /getHistoryItems endpoint, ideally limiting it to trusted internal networks or VPNs. Deploy web application firewalls (WAFs) with robust SQL injection detection and prevention rules to block malicious payloads targeting this endpoint. Monitor database logs and application logs for unusual query patterns or errors indicative of SQL injection attempts. Until an official patch is released, consider implementing input validation and sanitization at the application layer if source code access is available. Regularly back up databases to enable recovery in case of data tampering or loss. Engage with Siyuan developers or community forums to track patch releases and apply updates promptly. Additionally, conduct security assessments and penetration testing focused on SQL injection vectors to identify and remediate similar vulnerabilities in the environment.
Description
A SQL injection vulnerability was discovered in Siyuan 3.1.11 in /getHistoryItems.