# CVE-2026-124571: SourceCodester Simple CRUD using PHP and FPDF register.php sql injection


- **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/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-xjp7-vx43-w5mh

## What is CVE-2026-124571?

CVE-2026-124571 is a medium-severity vulnerability in SourceCodester Simple CRUD using PHP and FPDF, published on 9 Nov 2026. 

### Official description

A flaw has been found in SourceCodester Simple CRUD using PHP and FPDF 1.0. Affected by this vulnerability is an unknown functionality of the file app/register.php. Executing a manipulation of the argument firstname can lead to sql injection. The attack can be executed remotely. The exploit has been published 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-2026-124571?


## How do I fix CVE-2026-124571?

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

## Is CVE-2026-124571 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124571 and fix it if it is affected.

What it is: CVE-2026-124571 is a medium-severity vulnerability in SourceCodester Simple CRUD using PHP and FPDF, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124571 in the wild and no public exploit code.

Affected product: SourceCodester Simple CRUD using PHP and FPDF. 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-2026-124571/ (Markdown: https://insights.sbomify.com/CVE-2026-124571/index.md)
```

## Sources

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

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