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

> Reflected XSS in QingScan allows attackers to execute malicious scripts in victims' browsers via crafted URLs, potentially leading to session hijacking or data theft.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Feb 2025
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-jjvg-p7hw-35xj

## What is CVE-2024-57278?

CVE-2024-57278 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A reflected Cross-Site Scripting (XSS) vulnerability exists in /webscan/sqlmap/index.html in QingScan <=v1.8.0. The vulnerability is caused by improper input sanitization of the query parameter, allowing an attacker to inject malicious JavaScript payloads. When a victim accesses a crafted URL containing the malicious input, the script executes in the victim's browser context.

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

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


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

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

## Is CVE-2024-57278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-57278 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Feb 2025. Any signed-in user can exploit it over the network, 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-2024-57278 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-57278/ (Markdown: https://insights.sbomify.com/CVE-2024-57278/index.md)
```

## Sources

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

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