CVE-2025-41751
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_portCntr.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 · high confidenceA reflected XSS vulnerability in pxc_portCntr.php allows an unauthenticated remote attacker to craft malicious URLs that, when clicked by an authenticated user, can manipulate device configuration parameters accessible through the web-based management (WBM) interface. The httpOnly flag on session cookies prevents session hijacking, limiting impact to configuration parameter changes within the application's context.
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 the Phoenix Contact device modelAccess the web-based management (WBM) interface or check the device label/sticker to identify the exact model (e.g., FL NAT 2008, FL SWITCH 2008)Affected if The device model matches any of the affected products: FL NAT 2008, FL NAT 2208, FL NAT 2304 2gc 2sfp, FL SWITCH 2005, FL SWITCH 2008, FL SWITCH 2008f, FL SWITCH 2016, or FL SWITCH 2105
-
Determine the firmware versionLog into the WBM interface and navigate to System > Firmware or Status > Device Information to view the installed firmware versionAffected if The firmware version is lower than 3.50 (e.g., 3.40, 3.30, etc.)
-
Verify WBM web interface is accessibleAttempt to access the device's web interface via HTTP/HTTPS on the expected management IP addressAffected if The WBM interface is accessible and responds to requests
-
Check if pxc_portCntr.php is presentAccess the URL path /pxc_portCntr.php through the web interface (e.g., http://<device-ip>/pxc_portCntr.php)Affected if The pxc_portCntr.php script returns a valid HTTP response rather than a 404 error, indicating the vulnerable script exists on the device
-
Confirm user authentication is in useCheck if the WBM interface requires login credentials and if session cookies are set for authenticated usersAffected if The device has active user accounts configured and the WBM interface uses session-based authentication
The environment is affected if the device is one of the listed Phoenix Contact models running firmware version lower than 3.50 with the WBM interface accessible and the pxc_portCntr.php script present.
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 input validation and proper output encoding in pxc_portCntr.php to sanitize all user-supplied data before rendering it in the web interface. Consider adding CSRF tokens for configuration change requests to prevent authenticated users from inadvertently making unwanted changes via malicious links.
Firmware version 3.50 or later for FL Nat 2008, FL Nat 2208, FL Nat 2304 2gc 2sfp, FL Switch 2005, FL Switch 2008, FL Switch 2008f, FL Switch 2016, FL Switch 2105
- 1. Access the web-based management (WBM) interface of the affected Phoenix Contact FL NAT or FL Switch device
- 2. Navigate to the firmware update section in the device management settings
- 3. Download the firmware version 3.50 or later from the official Phoenix Contact support website (https://www.phoenixcontact.com)
- 4. Upload and apply the new firmware to the device
- 5. After the firmware update completes, verify the device is functioning normally and the WBM interface is accessible
- 6. Confirm the XSS vulnerability in pxc_portCntr.php is resolved by attempting to inject test payloads (or verify via vulnerability scan)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-41751 — 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-41751 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