# CVE-2024-44798: Cross-site scripting in n/a

> An attacker can inject malicious scripts via date parameters in the admin reports page, potentially stealing sessions or executing code.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 13 Sep 2024
- **Updated:** 13 Sep 2024
- **Also known as:** GHSA-jm4p-4c99-gp7x

## What is CVE-2024-44798?

CVE-2024-44798 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

phpgurukul Bus Pass Management System 1.0 is vulnerable to Cross-site scripting (XSS) in /admin/pass-bwdates-reports-details.php via fromdate and todate parameters.

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

## Which versions are affected by CVE-2024-44798?

It affects 1 product.


Products: Anujk305 Bus Pass Management System.

## How do I fix CVE-2024-44798?

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

## Is CVE-2024-44798 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-6288](https://insights.sbomify.com/CVE-2025-6288/): PHPGurukul Bus Pass Management System Profile Page admin-profile.php cross site scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44798 and fix it if it is affected.

What it is: CVE-2024-44798 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Sep 2024. 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-2024-44798 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-2024-44798/ (Markdown: https://insights.sbomify.com/CVE-2024-44798/index.md)
```

## Sources

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

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