# CVE-2025-4862: PHPGurukul Directory Management System searchdata.php cross site scripting

> Remote attackers can inject malicious scripts via the searchdata parameter in PHPGurukul Directory Management System, potentially compromising user sessions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 May 2025
- **Updated:** 20 May 2025
- **Also known as:** GHSA-jgf8-7wf7-3fr3

## What is CVE-2025-4862?

CVE-2025-4862 is a medium-severity cross-site scripting vulnerability in PHPGurukul Directory Management System, published on 18 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, has been found in PHPGurukul Directory Management System 2.0. Affected by this issue is some unknown functionality of the file /searchdata.php. The manipulation of the argument searchdata leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-4862?

It affects 1 product.


Products: Phpgurukul Directory Management System.

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

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

## Is CVE-2025-4862 being exploited?

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

## Other vulnerabilities in PHPGurukul Directory Management System

- [CVE-2022-31382](https://insights.sbomify.com/CVE-2022-31382/): SQL injection in n/a (critical 9.8)
- [CVE-2022-31383](https://insights.sbomify.com/CVE-2022-31383/): SQL injection in n/a (critical 9.8)
- [CVE-2022-31384](https://insights.sbomify.com/CVE-2022-31384/): SQL injection in n/a (critical 9.8)
- [CVE-2022-29006](https://insights.sbomify.com/CVE-2022-29006/): SQL injection in n/a (critical 9.8)
- [CVE-2026-1160](https://insights.sbomify.com/CVE-2026-1160/): PHPGurukul Directory Management System Search index.php sql injection (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4862 is a medium-severity cross-site scripting vulnerability in PHPGurukul Directory Management System, published on 18 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4862 exists.

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

## Sources

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

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