{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2025-25271 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-25271 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25271 is a high-severity vulnerability in Phoenix Contact CHARX SEC-3000, published on 8 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25271 and fix it if it is affected.\n\nWhat it is: CVE-2025-25271 is a high-severity vulnerability in Phoenix Contact CHARX SEC-3000, published on 8 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-25271 in the wild and no public exploit code.\n\nAffected product: Phoenix Contact CHARX SEC-3000. 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-25271/ (Markdown: https://insights.sbomify.com/CVE-2025-25271/index.md)","id":"CVE-2025-25271","markdown":"https://insights.sbomify.com/CVE-2025-25271/index.md","name":"CVE-2025-25271","record":{"aliases":["GHSA-q8vp-977j-9pjv"],"analysis":{"component_type":"network_device","fix_type":"configuration_change","impacts":["security_bypass","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging controller","requires_auth":"none","summary":"An unauthenticated adjacent attacker can configure a new OCPP backend due to insecure default settings in Phoenix Contact CHARX SEC devices.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[{"product":"charx_sec-3000_firmware","vendor":"phoenixcontact"},{"product":"charx_sec-3050_firmware","vendor":"phoenixcontact"},{"product":"charx_sec-3100_firmware","vendor":"phoenixcontact"},{"product":"charx_sec-3150_firmware","vendor":"phoenixcontact"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"An unauthenticated adjacent attacker is able to configure a new OCPP backend, due to insecure defaults for the configuration interface.","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":"OCPP Backend Configuration via Insecure Defaults","id":"CVE-2025-25271","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Intel(R) 700 Series Ethernet","id":"CVE-2025-25273"},"packages":[],"prev":{"headline":"Remote Code Execution via Unauthenticated Configuration Manipulation","id":"CVE-2025-25270"},"products":["CHARX SEC-3000","CHARX SEC-3050","CHARX SEC-3100","CHARX SEC-3150"],"published":"2025-07-08","related":[{"cvss_score":9.8,"headline":"Remote Code Execution via Unauthenticated Configuration Manipulation","id":"CVE-2025-25270","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":9.8,"headline":"PHOENIX CONTACT: Remote code execution in CHARX Series","id":"CVE-2024-25995","kev_date_added":null,"published":"2024-03-12"},{"cvss_score":8.8,"headline":"Unauthenticated Configuration Access via Exposed API Endpoint","id":"CVE-2025-25268","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":8.7,"headline":"PHOENIX CONTACT: Lack of SSL support in CHARX Series","id":"CVE-2024-26288","kev_date_added":null,"published":"2024-03-12"},{"cvss_score":8.6,"headline":"Phoenix Contact: update feature from CHARX controller can be used to reset a low privilege user password","id":"CVE-2024-6788","kev_date_added":null,"published":"2024-08-13"},{"cvss_score":8.4,"headline":"Local Privilege Escalation via Unauthenticated Command Injection","id":"CVE-2025-25269","kev_date_added":null,"published":"2025-07-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2025-07-22","vendors":["Phoenix Contact"]},"summary":"An unauthenticated adjacent attacker can configure a new OCPP backend due to insecure default settings in Phoenix Contact CHARX SEC devices.","url":"https://insights.sbomify.com/CVE-2025-25271/"}