# CVE-2025-5212: PHPGurukul Employee Record Management System editempexp.php sql injection

> SQL injection in the Employee Record Management System allows remote attackers to manipulate database queries via the emp1name parameter.

- **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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-rqxv-qh6g-hx7g

## What is CVE-2025-5212?

CVE-2025-5212 is a medium-severity SQL injection vulnerability in PHPGurukul Employee Record Management System, published on 26 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in PHPGurukul Employee Record Management System 1.3. It has been classified as critical. Affected is an unknown function of the file /admin/editempexp.php. The manipulation of the argument emp1name leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the 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-2025-5212?

It affects 1 product.


Products: Phpgurukul Employee Record Management System.

## How do I fix CVE-2025-5212?

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

## Is CVE-2025-5212 being exploited?

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

## Other vulnerabilities in PHPGurukul Employee Record Management System

- [CVE-2021-37782](https://insights.sbomify.com/CVE-2021-37782/): SQL injection in n/a (critical 9.8)
- [CVE-2021-44966](https://insights.sbomify.com/CVE-2021-44966/): SQL injection in n/a (critical 9.8)
- [CVE-2021-43451](https://insights.sbomify.com/CVE-2021-43451/): SQL injection in n/a (critical 9.8)
- [CVE-2020-35427](https://insights.sbomify.com/CVE-2020-35427/): SQL injection in n/a (critical 9.8)
- [CVE-2021-44965](https://insights.sbomify.com/CVE-2021-44965/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5212 and fix it if it is affected.

What it is: CVE-2025-5212 is a medium-severity SQL injection vulnerability in PHPGurukul Employee Record Management System, published on 26 May 2025. 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-2025-5212 exists.

Affected product: PHPGurukul Employee 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-2025-5212/ (Markdown: https://insights.sbomify.com/CVE-2025-5212/index.md)
```

## Sources

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

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