# CVE-2026-5575: SourceCodester/jkev Record Management System Login index.php sql injection

> Remote attackers can exploit SQL injection in the login form to access or modify database records in the Record Management System.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-jp5c-wr3p-x49r

## What is CVE-2026-5575?

CVE-2026-5575 is a medium-severity SQL injection vulnerability in SourceCodester Record Management System, published on 5 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in SourceCodester/jkev Record Management System 1.0. Affected by this vulnerability is an unknown functionality of the file index.php of the component Login. The manipulation of the argument Username results in sql injection. The attack may be launched remotely. The exploit is now 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-2026-5575?


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

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

## Is CVE-2026-5575 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5575 is a medium-severity SQL injection vulnerability in SourceCodester Record Management System, published on 5 Apr 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-2026-5575 exists.

Affected product: SourceCodester Record Management System. 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-5575/ (Markdown: https://insights.sbomify.com/CVE-2026-5575/index.md)
```

## Sources

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

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