# CVE-2020-29168: SQL injection in n/a

> Attackers can extract sensitive information via SQL injection in the getuser.php endpoint of the Online Doctor Appointment Booking System.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-hxq3-28qm-p5p4

## What is CVE-2020-29168?

CVE-2020-29168 is a critical SQL injection vulnerability in n/a, published on 17 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL Injection vulnerability in Projectworlds Online Doctor Appointment Booking System, allows attackers to gain sensitive information via the q parameter to the getuser.php endpoint.

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

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

It affects 1 product.


Products: Online Doctor Appointment Booking System Php and Mysql Project Online Doctor Appointment Booking System Php and Mysql.

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

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

## Is CVE-2020-29168 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-29283](https://insights.sbomify.com/CVE-2020-29283/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29168 is a critical SQL injection vulnerability in n/a, published on 17 Feb 2023. 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-29168 exists.

Affected product: n/a. 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-29168/ (Markdown: https://insights.sbomify.com/CVE-2020-29168/index.md)
```

## Sources

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

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