# CVE-2025-44180: Cross-site scripting in n/a

> Cross-site scripting vulnerability in Vehicle Record Management System allows attackers to inject malicious scripts via the brand ID parameter.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A: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:** 15 May 2025
- **Updated:** 15 May 2025
- **Also known as:** GHSA-gh72-rxwr-vvrq

## What is CVE-2025-44180?

CVE-2025-44180 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 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

Phpgurukul Vehicle Record Management System v1.0 is vulnerable to Cross Site Scripting (XSS) in /edit-brand.php?bid={brandId}.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Anujk305 Vehicle Record Management System.

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

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

## Is CVE-2025-44180 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-29641](https://insights.sbomify.com/CVE-2025-29641/): SQL injection in n/a (high 7.3)
- [CVE-2025-5913](https://insights.sbomify.com/CVE-2025-5913/): PHPGurukul Vehicle Record Management System search-vehicle.php sql injection (medium 6.9)
- [CVE-2025-44181](https://insights.sbomify.com/CVE-2025-44181/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-44182](https://insights.sbomify.com/CVE-2025-44182/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-44183](https://insights.sbomify.com/CVE-2025-44183/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44180 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 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-44180 exists.

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

## Sources

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

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