CVE-2025-41745
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_portCntr2.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.
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 stored XSS vulnerability exists in pxc_portCntr2.php where an unauthenticated attacker can inject malicious scripts via crafted POST requests that trick authenticated users into submitting manipulated requests to change WBM device configuration parameters. The attack is limited to web application configuration context and does not provide OS-level access or session hijacking due to httpOnly-protected cookies.
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 device's web interface (WBM) and navigate to System Information or Device Status page to confirm the exact model name (e.g., FL NAT 2008, FL Switch 2008, etc.)Affected if The device model matches one 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
-
Check the installed firmware versionIn the device's web interface, go to the Firmware or Software version section (typically under System Information or Administration > Firmware) and record the firmware version numberAffected if The firmware version is lower than 3.50 (for example, 3.48, 3.42, etc.)
-
Confirm the pxc_portCntr2.php endpoint existsAttempt to access the file pxc_portCntr2.php via the device's web interface by navigating to its URL path, or use a web vulnerability scanner to enumerate the web application's PHP filesAffected if The file pxc_portCntr2.php is present and accessible on the device's web server
-
Verify WBM interface accessibilityDetermine if the web-based management (WBM) interface is exposed to network access by checking the device's network configuration or by attempting to access the web interface from a remote locationAffected if The WBM interface is network-accessible (especially from untrusted networks) and accepts authenticated user sessions
The device is affected if it is a Phoenix Contact FL NAT or FL Switch model running firmware version below 3.50, and the pxc_portCntr2.php file exists on the accessible WBM interface.
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
Apply vendor patch for pxc_portCntr2.php implementing proper input sanitization and output encoding for all user-supplied parameters. Users should avoid clicking untrusted links until the patch is applied.
Firmware version 3.50
- Identify the specific device model from the affected product list (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)
- Locate the firmware download section on the vendor's support website (Phoenix Contact)
- Download firmware version 3.50 or later for your specific device model
- Review the firmware upgrade instructions in the product manual
- Backup the current device configuration
- Upload and apply the new firmware via the device's web-based management (WBM) interface or appropriate firmware update tool
- Verify the firmware version after upgrade to confirm 3.50 or later is installed
- Restore the configuration if needed and verify device functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41745 — 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-41745 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