# CVE-2025-5615: PHPGurukul Online Fire Reporting System details.php sql injection

> Remote attackers can exploit SQL injection in details.php to read or modify database contents in the Online Fire Reporting System.

- **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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2025
- **Updated:** 5 Jun 2025
- **Also known as:** GHSA-pjv5-ghj3-79pm

## What is CVE-2025-5615?

CVE-2025-5615 is a medium-severity SQL injection vulnerability in PHPGurukul Online Fire Reporting System, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in PHPGurukul Online Fire Reporting System 1.2. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /details.php. The manipulation of the argument requestid leads to sql injection. The attack can be launched 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-5615?

It affects 1 product.


Products: Phpgurukul Online Fire Reporting System.

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

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

## Is CVE-2025-5615 being exploited?

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

## Other vulnerabilities in PHPGurukul Online Fire Reporting System

- [CVE-2025-40687](https://insights.sbomify.com/CVE-2025-40687/): SQL injection in PHPGurukul Online Fire Reporting System (critical 9.3)
- [CVE-2025-40689](https://insights.sbomify.com/CVE-2025-40689/): SQL injection in PHPGurukul Online Fire Reporting System (critical 9.3)
- [CVE-2025-40690](https://insights.sbomify.com/CVE-2025-40690/): SQL injection in PHPGurukul Online Fire Reporting System (critical 9.3)
- [CVE-2025-40691](https://insights.sbomify.com/CVE-2025-40691/): SQL injection in PHPGurukul Online Fire Reporting System (critical 9.3)
- [CVE-2025-40692](https://insights.sbomify.com/CVE-2025-40692/): SQL injection in PHPGurukul Online Fire Reporting System (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5615 is a medium-severity SQL injection vulnerability in PHPGurukul Online Fire Reporting System, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5615 exists.

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

## Sources

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

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