# CVE-2025-1985: PEPPERL+FUCHS: Profinet Gateway LB8122A.1.EL – Device is affected by XSS vulnerability

> An unauthenticated remote attacker can inject HTML code into the Web-UI of the Profinet Gateway, potentially compromising user sessions or device integrity.

- **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:** 26 May 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-36jp-c3g9-9g26

## What is CVE-2025-1985?

CVE-2025-1985 is a medium-severity cross-site scripting vulnerability in Pepperl+Fuchs Profinet Gateway FB8122A.1.EL, published on 26 May 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

Due to improper neutralization of input during web page generation (XSS) an unauthenticated remote attacker can inject HTML code into the Web-UI in the affected device.

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

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


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

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

## Is CVE-2025-1985 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1985 is a medium-severity cross-site scripting vulnerability in Pepperl+Fuchs Profinet Gateway FB8122A.1.EL, published on 26 May 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-1985 in the wild and no public exploit code.

Affected product: Pepperl+Fuchs Profinet Gateway FB8122A.1.EL. 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-1985/ (Markdown: https://insights.sbomify.com/CVE-2025-1985/index.md)
```

## Sources

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

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