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

> Attackers can exploit SQL injection in the admin login panel to access or modify library data without proper authentication.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2020
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-mgc3-c66w-fpmm

## What is CVE-2020-25514?

CVE-2020-25514 is a high-severity SQL injection vulnerability in n/a, published on 22 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sourcecodester Simple Library Management System 1.0 is affected by Incorrect Access Control via the Login Panel, http://<site>/lms/admin.php.

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

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

It affects 1 product.


Products: Simple Library Management System Project Simple Library Management System.

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

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

## Is CVE-2020-25514 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25515](https://insights.sbomify.com/CVE-2020-25515/): File upload in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25514 is a high-severity SQL injection vulnerability in n/a, published on 22 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25514 in the wild and no public exploit code.

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-25514/ (Markdown: https://insights.sbomify.com/CVE-2020-25514/index.md)
```

## Sources

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

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