# CVE-2025-4028: PHPGurukul COVID19 Testing Management System profile.php sql injection

> Remote attackers can exploit SQL injection in profile.php to read or modify database contents in the COVID19 Testing 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-xg84-4r3q-gjjw

## What is CVE-2025-4028?

CVE-2025-4028 is a medium-severity SQL injection vulnerability in PHPGurukul COVID19 Testing Management System, published on 28 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in PHPGurukul COVID19 Testing Management System 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /profile.php. The manipulation of the argument mobilenumber leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

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-4028?

It affects 1 product.


Products: Phpgurukul Covid19 Testing Management System.

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

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

## Is CVE-2025-4028 being exploited?

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

Public exploit code:

- Published vulnerability reports by JunZ-Leo; credited reporter for CVE-2025-4028 and CVE-2025-4030. (github_poc): https://github.com/JunZ-Leo/CVE

## Other vulnerabilities in PHPGurukul COVID19 Testing Management System

- [CVE-2024-53604](https://insights.sbomify.com/CVE-2024-53604/): SQL injection in n/a (critical 9.8)
- [CVE-2021-33470](https://insights.sbomify.com/CVE-2021-33470/): SQL injection in n/a (critical 9.8)
- [CVE-2024-53603](https://insights.sbomify.com/CVE-2024-53603/): SQL injection in n/a (high 7.3)
- [CVE-2025-4174](https://insights.sbomify.com/CVE-2025-4174/): PHPGurukul COVID19 Testing Management System login.php sql injection (medium 6.9)
- [CVE-2025-4071](https://insights.sbomify.com/CVE-2025-4071/): PHPGurukul COVID19 Testing Management System test-details.php sql injection (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4028 is a medium-severity SQL injection vulnerability in PHPGurukul COVID19 Testing Management System, published on 28 Apr 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-4028 exists.

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

## Sources

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

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