dbcve.org
Ppc 2k05x FirmwareOperating system · Belden

CVE-2025-70545

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A stored cross-site scripting (XSS) vulnerability exists in the web management interface of the PPC (Belden) ONT 2K05X router running firmware v1.1.9_206L. The Common Gateway Interface (CGI) component improperly handles user-supplied input, allowing a remote, unauthenticated attacker to inject arbitrary JavaScript that is persistently stored and executed when the affected interface is accessed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in the CGI component of the web management interface on PPC (Belden) ONT 2K05X routers running firmware v1.1.9_206L. The vulnerability allows remote, unauthenticated attackers to inject malicious JavaScript that is persistently stored and executed whenever the affected interface is accessed.

MitigationImplement proper input validation and output encoding/sanitization in the CGI component to neutralize malicious script payloads before storage and before rendering in the browser.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ppc 2k05x FirmwareOperating system
Affected:= 1.1.9_206l

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the router's web management interface and navigate to the status or system information page to view the firmware version. Alternatively, check the device label or use SNMP or the router's CLI to retrieve the firmware version.
    Affected if The device is a Belden PPC 2K05X and the firmware version is exactly 1.1.9_206L
  2. Confirm web management interface accessibility
    Attempt to access the router's web interface over HTTP/HTTPS by entering the device's IP address in a web browser.
    Affected if The web management interface is accessible and responds to requests, indicating the CGI component is active
  3. Inspect stored CGI parameters for suspicious content
    Use browser developer tools to view the page source or intercept HTTP responses from the CGI component. Look for any JavaScript tags, event handlers, or encoded payloads in form fields, query parameters, or stored configuration values.
    Affected if Malicious JavaScript code (such as script tags or event handlers like onload, onerror) is present in stored CGI parameters or rendered in the interface
  4. Check browser for unexpected script execution
    Open the router's web interface in a browser and inspect the console tab in developer tools for any XSS-related errors or warnings, and monitor the network tab for unexpected script loading.
    Affected if Scripts execute automatically without user interaction or scripts are loaded from unexpected sources when accessing the management interface

You are affected if you are running Belden PPC 2K05X firmware version 1.1.9_206L and the web management interface displays or executes malicious script content stored in the CGI component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/sanitization in the CGI component to neutralize malicious script payloads before storage and before rendering in the browser.

Fix this in Ppc 2k05x Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-70545 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-70545 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data