CVE-2025-41748
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_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.
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 confidenceA reflected XSS vulnerability exists in pxc_Dot1xCfg.php where an unauthenticated attacker can craft malicious links that, when clicked by an authenticated user, execute arbitrary JavaScript in the victim's browser to manipulate web-based management (WBM) configuration parameters. The httpOnly flag on session cookies prevents session hijacking, limiting impact to the specific WBM configuration functions accessible through the affected script.
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 device modelLog into the web-based management (WBM) interface and locate the device model name (e.g., FL NAT 2008, FL Switch 2408) in the system information or status page. Alternatively, check the physical device label or use SNMP to query sysDescr.Affected if The device model matches one of the affected products listed in the CVE.
-
Check the installed firmware versionIn the WBM interface, navigate to the System > Info or System > Firmware section to view the current firmware version. Alternatively, check via CLI using 'show firmware' or SNMP OID if available.Affected if The firmware version is lower than 3.50 (e.g., 3.48, 3.40, etc.).
-
Confirm pxc_Dot1xCfg.php is accessibleAttempt to access the script directly via browser by navigating to https://<device_ip>/pxc_Dot1xCfg.php or checking if the URL responds with any content. This script is part of the Dot1x (IEEE 802.1X) configuration functionality.Affected if The script is reachable and returns a response, indicating the vulnerable endpoint is exposed.
You are affected if the device is one of the listed Phoenix Contact models AND the firmware version is below 3.50 AND the pxc_Dot1xCfg.php script is accessible in the 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 output encoding and input validation/sanitization in pxc_Dot1xCfg.php to neutralize malicious script content in user-controllable parameters. Consider implementing CSRF tokens for configuration change requests.
Firmware version 3.50 or later for the affected FL NAT and FL Switch device models
- 1. Identify the exact FL device model from the affected products list (e.g., FL NAT 2008, FL Switch 2005, etc.)
- 2. Access the device's web-based management (WBM) interface and navigate to the firmware or system information section
- 3. Document the current firmware version to confirm it is below 3.50
- 4. Download the firmware version 3.50 or later from the official vendor support website (Phoenix Contact)
- 5. Review the vendor's firmware upgrade instructions specific to your device model
- 6. Backup the current device configuration as a precaution
- 7. Upload and apply the new firmware version 3.50 or later via the WBM interface
- 8. After the upgrade completes, verify the new firmware version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41748 — 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-41748 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