Skip to main content
VulnerabilityPublished Updated

CVE-2024-53506: siyuan · SQL Injection

Affects siyuanSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Affected software

ProductAffectedFixed in
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threatsAffected
  • =3.1.11
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-53506, organizations should first check for and apply any official patches or updates released by Siyuan developers as soon as they become available. In the absence of a patch, implement strict input validation and sanitization on the 'ids' parameter to prevent malicious SQL code injection. Deploy web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the /batchGetBlockAttrs endpoint. Restrict network access to the vulnerable API endpoint by limiting it to trusted internal IP addresses or VPN users. Conduct thorough code reviews and security testing to identify and remediate similar injection flaws in other parts of the application. Monitor logs and network traffic for unusual database queries or error messages indicative of exploitation attempts. Educate developers on secure coding practices to prevent recurrence of SQL injection vulnerabilities. Finally, maintain regular backups of critical data to enable recovery in case of data corruption or deletion.

Description

A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the ids array parameter in /batchGetBlockAttrs.

References

Community reviews

Loading reviews…