Skip to main content
VulnerabilityPublished Updated

CVE-2024-53505: siyuan · SQL Injection

Affects siyuanSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 11:42 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 43% 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-53505, organizations should immediately check for and apply any official patches or updates released by Siyuan addressing this vulnerability. If patches are not yet available, implement web application firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the /getAssetContent endpoint and the 'id' parameter. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters passed to SQL queries. Employ parameterized queries or prepared statements in the application code to prevent injection. Restrict database user permissions to the minimum necessary to limit potential damage. Monitor logs for unusual database query patterns or errors indicative of injection attempts. Consider network segmentation to isolate Siyuan servers and limit exposure. Finally, maintain an incident response plan ready to address potential exploitation and data breaches.

Description

A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the id parameter at /getAssetContent.

References

Community reviews

Loading reviews…