# CVE-2026-6997: BDCOM P3310D New RMON History cross site scripting

> An attacker can inject malicious scripts into the New RMON History page of BDCOM P3310D devices, potentially compromising user sessions.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-mfxp-4pf4-x8m8

## What is CVE-2026-6997?

CVE-2026-6997 is a medium-severity cross-site scripting vulnerability in BDCOM P3310D, published on 25 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A security vulnerability has been detected in BDCOM P3310D 0.4.2 10.1.0F Build 86345. This impacts an unknown function of the component New RMON History Page. The manipulation of the argument Owner leads to cross site scripting. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-6997?


## How do I fix CVE-2026-6997?

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

## Is CVE-2026-6997 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6997 and fix it if it is affected.

What it is: CVE-2026-6997 is a medium-severity cross-site scripting vulnerability in BDCOM P3310D, published on 25 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-6997 in the wild and no public exploit code.

Affected product: BDCOM P3310D. 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-2026-6997/ (Markdown: https://insights.sbomify.com/CVE-2026-6997/index.md)
```

## Sources

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

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