# CVE-2025-3818: webpy web.py db.py PostgresDB._process_insert_query sql injection

> Remote attackers can exploit SQL injection in web.py's PostgresDB insert query processing to read or modify database contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Apr 2025
- **Updated:** 29 May 2025
- **Also known as:** DEBIAN-CVE-2025-3818, DLA-4189-1, GHSA-9g47-36rw-gjh2, UBUNTU-CVE-2025-3818, USN-8443-1

## What is CVE-2025-3818?

CVE-2025-3818 is a medium-severity SQL injection vulnerability in webpy web.py, published on 19 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in webpy web.py 0.70. Affected is the function PostgresDB._process_insert_query of the file web/db.py. The manipulation of the argument seqname leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-3818?


## How do I fix CVE-2025-3818?

Apply the vendor's patch.

## Is CVE-2025-3818 being exploited?

There is no known exploitation of CVE-2025-3818 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3818 and fix it if it is affected.

What it is: CVE-2025-3818 is a medium-severity SQL injection vulnerability in webpy web.py, published on 19 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3818 in the wild and no public exploit code.

Affected product: webpy web.py. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3818/ (Markdown: https://insights.sbomify.com/CVE-2025-3818/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3818
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3818
- OSV: https://osv.dev/vulnerability/CVE-2025-3818

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3818/
Summaries are generated and may contain mistakes; the official description above is the record.