CVE-2025-41747
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_vlanIntfCfg.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_vlanIntfCfg.php where an unauthenticated attacker can inject malicious script through manipulated POST requests. The attack requires tricking an authenticated user into submitting the crafted request to alter WBM configuration parameters. While the httpOnly flag prevents session hijacking, the XSS can still modify device VLAN interface settings.
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 modelAccess the device web interface or use SNMP/SSH to query the device model. Look for model identifiers: 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.Affected if The device model matches one of the listed affected products.
-
Check firmware versionIn the WBM interface, navigate to System > Firmware or use CLI command 'show firmware-version' via SSH/Telnet. Compare the installed version against 3.50.Affected if Firmware version is below 3.50.
-
Verify WBM is enabledCheck if the web-based management interface is accessible. In CLI, verify HTTP/HTTPS service is running using 'show services' or check WBM settings in System > Network > WebBasedManagement.Affected if WBM interface (HTTP or HTTPS) is enabled and accessible.
-
Confirm VLAN configuration accessNavigate to the WBM interface and check if VLAN interface configuration page (pxc_vlanIntfCfg.php or similar VLAN settings) is reachable and accessible to authenticated users.Affected if VLAN interface configuration feature is available in the WBM.
-
Inspect for existing XSS payloadsReview the VLAN interface configuration parameters in the WBM or via API for any unexpected script tags, HTML content, or malformed values that may indicate prior exploitation.Affected if Stored XSS payloads or suspicious content is found in VLAN configuration fields.
The device is affected if it is a Phoenix Contact FL NAT or FL Switch model with firmware below 3.50 and the WBM interface with VLAN configuration is enabled.
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 for all parameters in pxc_vlanIntfCfg.php, and add CSRF tokens to prevent forced authenticated requests.
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, and FL Switch 2105
- 1. Identify the specific FL NAT or FL Switch 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)
- 2. Access the device's web-based management (WBM) interface
- 3. Navigate to the system information or firmware management section to check the current firmware version
- 4. Download firmware version 3.50 or later from the vendor's official support website (certvde.com or vendor direct)
- 5. Follow the vendor's documented firmware upgrade procedure, typically found in the device manual
- 6. After upgrading, verify the firmware version shows 3.50 or higher
- 7. Test that the pxc_vlanIntfCfg.php functionality works correctly with the new firmware
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41747 — 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-41747 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