CVE-2025-41752
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_portSfp.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 confidenceAn XSS vulnerability in pxc_portSfp.php allows an unauthenticated remote attacker to craft malicious links that, when clicked by an authenticated user, execute JavaScript in the user's browser context to manipulate device configuration parameters accessible through the web-based management (WBM) interface.
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.
-
Check installed firmware versionAccess the web-based management interface and navigate to System > Information or use SSH to run 'show firmware-version' or check the system info pageAffected if The displayed firmware version is less than 3.50 (e.g., 3.40, 3.30, etc.)
-
Confirm WBM interface is enabledVerify that the web-based management interface is accessible by navigating to the device IP in a browser or checking HTTP/HTTPS service statusAffected if The WBM interface is active and reachable on the network
-
Identify the vulnerable script presenceAttempt to access pxc_portSfp.php via the web interface (e.g., https://device-ip/pxc_portSfp.php) or check file system if SSH access is availableAffected if The script returns a response rather than a 404 error, indicating it exists on the device
-
Review web access logs for suspicious parametersExamine the device web server logs or proxy logs for requests to pxc_portSfp.php containing suspicious JavaScript patterns like <script>, javascript:, or onerror=Affected if Malicious XSS payloads are present in recent access logs targeting the vulnerable endpoint
You are affected if your device runs firmware version低于3.50 and the WBM interface is accessible with pxc_portSfp.php present on the system.
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_portSfp.php to sanitize user-supplied data before rendering in HTML. Additionally, users should be advised not to click on untrusted links.
Firmware version 3.50 or later for the affected FL NAT and FL Switch devices
- 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, FL Switch 2105)
- Navigate to the device's web-based management (WBM) interface
- Locate the firmware upgrade section in the administration or system settings
- Obtain the firmware version 3.50 or later from the vendor's official support website (certvde.com or manufacturer)
- Upload and install the firmware update following the vendor's documented upgrade procedure
- After upgrade, verify the pxc_portSfp.php page no longer reflects unsanitized input
- Confirm the web application now properly escapes or encodes user-supplied data in the affected component
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-41752 — 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-41752 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