# CVE-2025-34182: Deciso OPNsense < 25.7.4 /interfaces_ppps_edit.php ptpid Stored XSS

> Authenticated attackers can inject malicious scripts via the ptpid parameter in OPNsense, leading to stored XSS and potential session hijacking.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA: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:** 1 Oct 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-v8ch-859h-ggwh

## What is CVE-2025-34182?

CVE-2025-34182 is a medium-severity cross-site scripting vulnerability in Deciso OPNsense, published on 1 Oct 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

In Deciso OPNsense before 25.7.4, when creating an "Interfaces: Devices: Point-to-Point" entry, the value of the parameter ptpid is not sanitized of HTML-related characters/strings. This value is directly displayed when visiting the page/interfaces_assign.php, which can result in stored cross-site scripting. The attacker must be authenticated with at-least "Interfaces: PPPs: Edit" permission. This vulnerability has been addressed by the vendor in the product release notes as "ui: legacy_html_escape_form_data() was not escaping keys only data elements."

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

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


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

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

## Is CVE-2025-34182 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34182 is a medium-severity cross-site scripting vulnerability in Deciso OPNsense, published on 1 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-34182 in the wild and no public exploit code.

Affected product: Deciso OPNsense. 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-34182/ (Markdown: https://insights.sbomify.com/CVE-2025-34182/index.md)
```

## Sources

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

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