Unauthenticated local file read via SQL injection
Published Jul 5, 2024 · Updated Oct 15, 2025
SQL injection in Vanna 0.3.4 and earlier allows remote attackers to read arbitrary server files through an exposed Flask API. The API executes attacker-influenced PostgreSQL queries without neutralizing SQL syntax, permitting file-reading functions such as pg_read_file() to access local paths. No authentication is required, but exploitation depends on a Flask deployment connected to PostgreSQL with permission to read the targeted file.
Summary
What happened
SQL injection in Vanna 0.3.4 and earlier allows remote attackers to read arbitrary server files through an exposed Flask API. The API executes attacker-influenced PostgreSQL queries without neutralizing SQL syntax, permitting file-reading functions such as pg_read_file() to access local paths. No authentication is required, but exploitation depends on a Flask deployment connected to PostgreSQL with permission to read the targeted file.
The record
- CVE
- CVE-2024-5753
- Published
- Jul 5, 2024
- Updated
- Oct 15, 2025
- Vendor
- Vanna AI
- Product
- Vanna
- Classifications
- CWE-89, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 5, 2024CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.3.4
- Affected versionversion=unspecified <=latest
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo