CVE intelligence and bounded remediation

CVE-2025-41746 — Phoenixcontact Fl Switch 2406-2Sfx Pn Firmware security vulnerability

High CVSS 7.1

An XSS vulnerability in pxc_portSecCfg.php can be used by an unauthenticated remote attacker to trick an authenticated user to send a manipulated POST request to the device in order to change parameters available via web based management (WBM). The vulnerability does not provide access to system-level resources such as operating system internals or privileged functions. Access is limited to device configuration parameters that are available in the context of the web application. The session cookie is secured by the httpOnly Flag. Therefore an attacker is not able to take over the session of an authenticated user.

Severity
High
CVSS
7.1 (3.1)
Published
2025-12-09
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-79

Affected products

  • phoenixcontact / fl_switch_2406-2sfx_pn_firmware
  • phoenixcontact / fl_switch_2408_firmware
  • phoenixcontact / fl_switch_2408_pn_firmware
  • phoenixcontact / fl_switch_2412-2tc-2sfx_firmware
  • phoenixcontact / fl_switch_2414-2sfx_firmware
  • phoenixcontact / fl_switch_2414-2sfx_pn_firmware

Showing 6 representative product identities from 69 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Cross-site scripting and unsafe browser output

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
  • Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
  • Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.

Remediate safely

  • Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
  • Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
  • Update affected rendering components and add tests for every output context using inert sentinel markup.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.