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

> Remote attackers can execute arbitrary code via crafted GET requests to the Sensaphone WEB600 Monitoring System.

- **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:** 21 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-qw3x-33f8-7ff3

## What is CVE-2024-55040?

CVE-2024-55040 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jul 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

Cross Site Scripting vulnerability in Sensaphone WEB600 Monitoring System v.1.6.5.H and before allows a remote attacker to execute arbitrary code via a crafted GET requests to /@.xml, placing payloads in the g7200, g7300, g4601, and g1F02 parameters.

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

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

It affects 1 product.


Products: Sensaphone Web600 Firmware.

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

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

## Is CVE-2024-55040 being exploited?

There is no known exploitation of CVE-2024-55040 in the wild and no public exploit code.

Public exploit code:

- Public disclose of several stored XSS vulnerabilities in the Sensaphone WEB600 (CVE-2024-55040) (github_poc): https://github.com/tcbutler320/CVE-2024-55040-Sensaphone-XSS

## Fix prompt for AI coding agents

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

What it is: CVE-2024-55040 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jul 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: There is no known exploitation of CVE-2024-55040 in the wild and no public exploit code.

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

## Sources

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

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