{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40742 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-40742 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-40742 is a medium-severity vulnerability in Siemens SIPROTEC 5 6MD84 (CP300), published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-40742 and fix it if it is affected.\n\nWhat it is: CVE-2025-40742 is a medium-severity vulnerability in Siemens SIPROTEC 5 6MD84 (CP300), published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-40742 in the wild and no public exploit code.\n\nAffected product: Siemens SIPROTEC 5 6MD84 (CP300). 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-40742/ (Markdown: https://insights.sbomify.com/CVE-2025-40742/index.md)","id":"CVE-2025-40742","markdown":"https://insights.sbomify.com/CVE-2025-40742/index.md","name":"CVE-2025-40742","record":{"aliases":["GHSA-2qhm-4w63-5pph"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Siemens SIPROTEC 5","requires_auth":"none","summary":"An attacker can obtain sensitive information from Siemens SIPROTEC 5 devices due to improper handling of sensitive data in transit.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"siemens","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-598","name":"Use of HTTP Request With Sensitive Query String"}],"description":"A vulnerability has been identified in SIPROTEC 5 6MD84 (CP300) (All versions \u003c V11.0), SIPROTEC 5 6MD85 (CP200) (All versions), SIPROTEC 5 6MD85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 6MD86 (CP200) (All versions), SIPROTEC 5 6MD86 (CP300) (All versions \u003c V11.0), SIPROTEC 5 6MD89 (CP300) (All versions \u003c V11.0), SIPROTEC 5 6MD89 (CP300) V9.6x (All versions \u003c V11.0), SIPROTEC 5 6MU85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7KE85 (CP200) (All versions), SIPROTEC 5 7KE85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SA82 (CP100) (All versions), SIPROTEC 5 7SA82 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7SA84 (CP200) (All versions), SIPROTEC 5 7SA86 (CP200) (All versions), SIPROTEC 5 7SA86 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SA87 (CP200) (All versions), SIPROTEC 5 7SA87 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SD82 (CP100) (All versions), SIPROTEC 5 7SD82 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7SD84 (CP200) (All versions), SIPROTEC 5 7SD86 (CP200) (All versions), SIPROTEC 5 7SD86 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SD87 (CP200) (All versions), SIPROTEC 5 7SD87 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SJ81 (CP100) (All versions), SIPROTEC 5 7SJ81 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7SJ82 (CP100) (All versions), SIPROTEC 5 7SJ82 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7SJ85 (CP200) (All versions), SIPROTEC 5 7SJ85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SJ86 (CP200) (All versions), SIPROTEC 5 7SJ86 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SK82 (CP100) (All versions), SIPROTEC 5 7SK82 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7SK85 (CP200) (All versions), SIPROTEC 5 7SK85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SL82 (CP100) (All versions), SIPROTEC 5 7SL82 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7SL86 (CP200) (All versions), SIPROTEC 5 7SL86 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SL87 (CP200) (All versions), SIPROTEC 5 7SL87 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SS85 (CP200) (All versions), SIPROTEC 5 7SS85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7ST85 (CP200) (All versions), SIPROTEC 5 7ST85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7ST86 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SX82 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7SX85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7SY82 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7UM85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7UT82 (CP100) (All versions), SIPROTEC 5 7UT82 (CP150) (All versions \u003c V11.0), SIPROTEC 5 7UT85 (CP200) (All versions), SIPROTEC 5 7UT85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7UT86 (CP200) (All versions), SIPROTEC 5 7UT86 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7UT87 (CP200) (All versions), SIPROTEC 5 7UT87 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7VE85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7VK87 (CP200) (All versions), SIPROTEC 5 7VK87 (CP300) (All versions \u003c V11.0), SIPROTEC 5 7VU85 (CP300) (All versions \u003c V11.0), SIPROTEC 5 Compact 7SX800 (CP050) (All versions \u003c V11.0). The affected devices include session identifiers in URL requests for certain functionalities. This could allow an attacker to retrieve sensitive session data from browser history, logs, or other storage mechanisms, potentially leading to unauthorized access.","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":"Information disclosure in SIPROTEC 5 6MD84 (CP300)","id":"CVE-2025-40742","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in SINUMERIK 828D PPU.4","id":"CVE-2025-40743"},"packages":[],"prev":{"headline":"Memory corruption in Solid Edge SE2025","id":"CVE-2025-40741"},"products":["SIPROTEC 5 6MD84 (CP300)","SIPROTEC 5 6MD85 (CP200)","SIPROTEC 5 6MD85 (CP300)","SIPROTEC 5 6MD86 (CP200)","SIPROTEC 5 6MD86 (CP300)","SIPROTEC 5 6MD89 (CP300)","SIPROTEC 5 6MD89 (CP300) V9.6x","SIPROTEC 5 6MU85 (CP300)","SIPROTEC 5 7KE85 (CP200)","SIPROTEC 5 7KE85 (CP300)","SIPROTEC 5 7SA82 (CP100)","SIPROTEC 5 7SA82 (CP150)","SIPROTEC 5 7SA84 (CP200)","SIPROTEC 5 7SA86 (CP200)","SIPROTEC 5 7SA86 (CP300)","SIPROTEC 5 7SA87 (CP200)","SIPROTEC 5 7SA87 (CP300)","SIPROTEC 5 7SD82 (CP100)","SIPROTEC 5 7SD82 (CP150)","SIPROTEC 5 7SD84 (CP200)","SIPROTEC 5 7SD86 (CP200)","SIPROTEC 5 7SD86 (CP300)","SIPROTEC 5 7SD87 (CP200)","SIPROTEC 5 7SD87 (CP300)","SIPROTEC 5 7SJ81 (CP100)","SIPROTEC 5 7SJ81 (CP150)","SIPROTEC 5 7SJ82 (CP100)","SIPROTEC 5 7SJ82 (CP150)","SIPROTEC 5 7SJ85 (CP200)","SIPROTEC 5 7SJ85 (CP300)","SIPROTEC 5 7SJ86 (CP200)","SIPROTEC 5 7SJ86 (CP300)","SIPROTEC 5 7SK82 (CP100)","SIPROTEC 5 7SK82 (CP150)","SIPROTEC 5 7SK85 (CP200)","SIPROTEC 5 7SK85 (CP300)","SIPROTEC 5 7SL82 (CP100)","SIPROTEC 5 7SL82 (CP150)","SIPROTEC 5 7SL86 (CP200)","SIPROTEC 5 7SL86 (CP300)","SIPROTEC 5 7SL87 (CP200)","SIPROTEC 5 7SL87 (CP300)","SIPROTEC 5 7SS85 (CP200)","SIPROTEC 5 7SS85 (CP300)","SIPROTEC 5 7ST85 (CP200)","SIPROTEC 5 7ST85 (CP300)","SIPROTEC 5 7ST86 (CP300)","SIPROTEC 5 7SX82 (CP150)","SIPROTEC 5 7SX85 (CP300)","SIPROTEC 5 7SY82 (CP150)","SIPROTEC 5 7UM85 (CP300)","SIPROTEC 5 7UT82 (CP100)","SIPROTEC 5 7UT82 (CP150)","SIPROTEC 5 7UT85 (CP200)","SIPROTEC 5 7UT85 (CP300)","SIPROTEC 5 7UT86 (CP200)","SIPROTEC 5 7UT86 (CP300)","SIPROTEC 5 7UT87 (CP200)","SIPROTEC 5 7UT87 (CP300)","SIPROTEC 5 7VE85 (CP300)","SIPROTEC 5 7VK87 (CP200)","SIPROTEC 5 7VK87 (CP300)","SIPROTEC 5 7VU85 (CP300)","SIPROTEC 5 Compact 7SX800 (CP050)"],"published":"2025-07-08","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":"partial"},"state":"PUBLISHED","updated":"2026-05-12","vendors":["Siemens"]},"summary":"An attacker can obtain sensitive information from Siemens SIPROTEC 5 devices due to improper handling of sensitive data in transit.","url":"https://insights.sbomify.com/CVE-2025-40742/"}