CVE-2025-41750
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 · uneditedAn XSS vulnerability in pxc_PortCfg.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.
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 confidenceAn XSS vulnerability in pxc_PortCfg.php allows unauthenticated remote attackers to craft malicious links that, when clicked by authenticated users, execute arbitrary JavaScript in the user's browser context. This enables manipulation of device configuration parameters accessible through the web-based management (WBM) interface, though system-level access and session hijacking are prevented by httpOnly cookie protection.
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< 3.50< 3.50< 3.50< 3.50< 3.50< 3.50< 3.50< 3.50CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the Phoenix Contact Fl Switch WBM interface (web-based management) and navigate to System Information or Device Status to view the firmware version. Alternatively, check the device's web interface for a firmware version display.Affected if The device is a Fl Switch model (2008f, 2016, 2105, 2108, 2116, 2204 2tc 2sfx, 2205, or 2206 2fx) running firmware version 3.49 or lower.
-
Confirm WBM interface is accessibleVerify that the web-based management interface is reachable over the network by accessing the device's IP address in a web browser.Affected if The WBM interface is exposed and accessible to network users.
-
Check if authentication is required for WBMVerify whether the pxc_PortCfg.php endpoint requires valid credentials by attempting to access it or checking the authentication configuration in the WBM interface.Affected if The WBM interface allows access without authentication or permits authenticated users to access the configuration endpoints.
-
Verify pxc_PortCfg.php exists and is accessibleAttempt to access the pxc_PortCfg.php file directly through the web interface (e.g., https://device-ip/pxc_PortCfg.php) to confirm the vulnerable script is present.Affected if The pxc_PortCfg.php file exists and responds to requests, indicating the vulnerable component is present on the device.
The device is affected if it is a Fl Switch model from the list running firmware version below 3.50, has its WBM interface accessible, and contains the pxc_PortCfg.php script.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped3.50
Implement proper input validation and output encoding in pxc_PortCfg.php to neutralize XSS payloads, and consider adding Content-Security-Policy headers and CSRF tokens for configuration change requests.
Firmware 3.50
- Access the FL Switch web-based management (WBM) interface
- Navigate to System > Firmware or similar firmware update section
- Check the current firmware version to confirm it is below 3.50
- Download firmware version 3.50 or later from the official Phoenix Contact/Hirschmann support website (ensure authenticity via certvde.com or vendor directly)
- Upload the firmware file via the web interface or appropriate update method
- Wait for the firmware update to complete and the device to reboot
- Verify the new firmware version is 3.50 or later
- Log in again and verify that pxc_PortCfg.php no longer reflects unsanitized input in the URL parameters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-41750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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