CVE-2025-41748: Phoenix Contact FL SWITCH 2005 · Cross-site Scripting
Affects Phoenix Contact FL SWITCH 2005Source CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 9.7% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Phoenix Contact FL SWITCH 2005 | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Restrict access to the FL SWITCH 2005 web management interface to trusted networks and IP addresses using network segmentation and firewall rules. 2) Employ multi-factor authentication (MFA) for accessing management interfaces to reduce the risk of unauthorized access. 3) Educate users about phishing and social engineering risks to minimize the chance of clicking malicious links. 4) Monitor network traffic and device logs for unusual configuration changes or access patterns indicative of exploitation attempts. 5) Implement web application firewalls (WAFs) or intrusion prevention systems (IPS) that can detect and block XSS payloads targeting the management interface. 6) Coordinate with Phoenix Contact for timely patch releases and apply updates as soon as they become available. 7) Where possible, disable or limit web-based management interfaces and use alternative secure management methods such as out-of-band management. 8) Conduct regular security assessments and penetration testing focused on OT environments to identify and remediate similar vulnerabilities.
Description
An XSS vulnerability in pxc_Dot1xCfg.php can be used by an unauthenticated remote attacker to trick an authenticated user to click on the link provided by the attacker 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.