# CVE-2020-37083: addressbook 9.0.0.1 - 'id' SQL Injection

> Remote attackers can extract database information via time-based blind SQL injection in the photo.php endpoint of PHP Address Book.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-p3xh-76cc-cfqr

## What is CVE-2020-37083?

CVE-2020-37083 is a high-severity SQL injection vulnerability in chatelao PHP Address Book, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP AddressBook 9.0.0.1 contains a time-based blind SQL injection vulnerability that allows remote attackers to manipulate database queries through the 'id' parameter. Attackers can inject crafted SQL statements with time delays to extract information by observing response times in the photo.php endpoint.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2020-37083?


## How do I fix CVE-2020-37083?

No fix has been published for CVE-2020-37083 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-37083 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37083 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37083 and fix it if it is affected.

What it is: CVE-2020-37083 is a high-severity SQL injection vulnerability in chatelao PHP Address Book, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37083 exists.

Affected product: chatelao PHP Address Book. 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-2020-37083/ (Markdown: https://insights.sbomify.com/CVE-2020-37083/index.md)
```

## Sources

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

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