{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-41669 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-41669 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-41669 is a high-severity code injection vulnerability in Phoenix Contact AXC F 1152, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-41669 and fix it if it is affected.\n\nWhat it is: CVE-2025-41669 is a high-severity code injection vulnerability in Phoenix Contact AXC F 1152, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-41669 in the wild and no public exploit code.\n\nAffected product: Phoenix Contact AXC F 1152. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-41669/ (Markdown: https://insights.sbomify.com/CVE-2025-41669/index.md)","id":"CVE-2025-41669","markdown":"https://insights.sbomify.com/CVE-2025-41669/index.md","name":"CVE-2025-41669","record":{"aliases":["GHSA-m3wg-2ch3-59m2"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"PLCnext Control","requires_auth":"low_privilege","summary":"Remote low-privileged users can install unverified apps to achieve root code execution on PLCnext Control devices.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The Web-based Management allows a remote low privileged Engineer user to install additional APPs on the device downloaded from the PLCnext Store without implementing any data verification mechanism, leading to the capability for an Engineer user to reach arbitrary code execution with root privileges on the PLC device. A successful exploitation may allow to install a manipulated APP package, potentially impacting integrity and availability of the PLCnext Control.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Insufficient Verification of Data Authenticity","id":"CVE-2025-41669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Untrusted Search Path","id":"CVE-2025-41670"},"packages":[],"prev":{"headline":"Phoenix Contact: File access due to the replacement of a critical file used by the service security-profile","id":"CVE-2025-41668"},"products":["AXC F 1152","AXC F 1252","AXC F 2000 EA","AXC F 2152","AXC F 3152","BPC 9102S","EPC 1522","RFC 4072R","RFC 4072S","VL3 UPC 2440 EDGE","VPLCNEXT CONTROL 1000","VPLCNEXT CONTROL 2000","VPLCNEXT CONTROL 3000","VPLCNEXT CONTROL 500"],"published":"2026-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["Phoenix Contact"]},"summary":"Remote low-privileged users can install unverified apps to achieve root code execution on PLCnext Control devices.","url":"https://insights.sbomify.com/CVE-2025-41669/"}