# CVE-2025-55054: Cross-site scripting in EG7035E-M11

> Cross-site scripting vulnerability in Baicells EG7035E-M11 allows attackers to inject malicious scripts into web pages viewed by other users.

- **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:** 9 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-5g2c-gfqc-pgx7

## What is CVE-2025-55054?

CVE-2025-55054 is a medium-severity cross-site scripting vulnerability in Baicells EG7035E-M11, published on 9 Sep 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

CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting')

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

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


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

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

## Is CVE-2025-55054 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55054 is a medium-severity cross-site scripting vulnerability in Baicells EG7035E-M11, published on 9 Sep 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-2025-55054 in the wild and no public exploit code.

Affected product: Baicells EG7035E-M11. 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-55054/ (Markdown: https://insights.sbomify.com/CVE-2025-55054/index.md)
```

## Sources

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

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