SQL injection via unescaped sequence name
Published Apr 19, 2025 · Updated May 29, 2025
SQL injection in web.py 0.70 allows remote authenticated users to read or alter PostgreSQL data through a crafted sequence name. PostgresDB._process_insert_query appends seqname directly inside a quoted currval() statement without validation or parameterization. Reachability requires an application path that lets a low-privileged remote user influence the sequence name passed to a PostgreSQL insert.
Summary
What happened
SQL injection in web.py 0.70 allows remote authenticated users to read or alter PostgreSQL data through a crafted sequence name. PostgresDB._process_insert_query appends seqname directly inside a quoted currval() statement without validation or parameterization. Reachability requires an application path that lets a low-privileged remote user influence the sequence name passed to a PostgreSQL insert.
The record
- CVE
- CVE-2025-3818
- Published
- Apr 19, 2025
- Updated
- May 29, 2025
- Vendor
- web.py
- Product
- web.py
- Classifications
- CWE-74, CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 19, 2025CVE publishedPublication date reported by the CVE source.
- May 29, 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.70
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
- web.py sequence-name SQL injection proof of conceptproof of concept · unverified
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