# CVE-2025-41747: Reflected XSS vulnerability in pxc_vlanIntfCfg.php > Unauthenticated attackers can trick authenticated users into modifying device configuration parameters via reflected XSS in the web management interface. - **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 9 Dec 2025 - **Updated:** 9 Dec 2025 - **Also known as:** GHSA-35pj-p27v-5rpc ## What is CVE-2025-41747? CVE-2025-41747 is a high-severity cross-site scripting vulnerability in Phoenix Contact FL NAT 2008, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description An 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-41747? It affects 69 products. Products: Phoenixcontact Fl Nat 2008 Firmware, Phoenixcontact Fl Nat 2208 Firmware, Phoenixcontact Fl Nat 2304-2gc-2sfp Firmware, Phoenixcontact Fl Switch 2005 Firmware, Phoenixcontact Fl Switch 2008 Firmware, Phoenixcontact Fl Switch 2008f Firmware, Phoenixcontact Fl Switch 2016 Firmware, Phoenixcontact Fl Switch 2105 Firmware, Phoenixcontact Fl Switch 2108 Firmware, Phoenixcontact Fl Switch 2116 Firmware, Phoenixcontact Fl Switch 2204-2tc-2sfx Firmware, Phoenixcontact Fl Switch 2205 Firmware, Phoenixcontact Fl Switch 2206-2fx Firmware, Phoenixcontact Fl Switch 2206-2fx Sm Firmware, Phoenixcontact Fl Switch 2206-2fx Sm St Firmware, Phoenixcontact Fl Switch 2206-2fx St Firmware, Phoenixcontact Fl Switch 2206-2sfx Firmware, Phoenixcontact Fl Switch 2206-2sfx Pn Firmware, Phoenixcontact Fl Switch 2206c-2fx Firmware, Phoenixcontact Fl Switch 2207-Fx Firmware and 49 more. ## How do I fix CVE-2025-41747? No fix has been published for CVE-2025-41747 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-41747 being exploited? There is no known exploitation of CVE-2025-41747 in the wild and no public exploit code. ## Other vulnerabilities in Phoenix Contact FL NAT 2008 - [CVE-2025-41695](https://insights.sbomify.com/CVE-2025-41695/): Reflected XSS vulnerability in dyn_conn.php (high 7.1) - [CVE-2025-41745](https://insights.sbomify.com/CVE-2025-41745/): Reflected XSS vulnerability in pxc_portCntr2.php (high 7.1) - [CVE-2025-41746](https://insights.sbomify.com/CVE-2025-41746/): Reflected XSS vulnerability in pxc_portSecCfg.php (high 7.1) - [CVE-2025-41748](https://insights.sbomify.com/CVE-2025-41748/): Reflected XSS vulnerability in pxc_Dot1xCfg.php (high 7.1) - [CVE-2025-41749](https://insights.sbomify.com/CVE-2025-41749/): Reflected XSS vulnerability in port_util.php (high 7.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-41747 and fix it if it is affected. What it is: CVE-2025-41747 is a high-severity cross-site scripting vulnerability in Phoenix Contact FL NAT 2008, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-41747 in the wild and no public exploit code. Affected product: Phoenix Contact FL NAT 2008. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-41747/ (Markdown: https://insights.sbomify.com/CVE-2025-41747/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-41747 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-41747 - OSV: https://osv.dev/vulnerability/CVE-2025-41747 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-41747/ Summaries are generated and may contain mistakes; the official description above is the record.