{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52162 exists.","fix":"No fix has been published for CVE-2025-52162 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52162 is a medium-severity vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52162 and fix it if it is affected.\n\nWhat it is: CVE-2025-52162 is a medium-severity vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52162 exists.\n\nAffected product: n/a. 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-52162/ (Markdown: https://insights.sbomify.com/CVE-2025-52162/index.md)","id":"CVE-2025-52162","markdown":"https://insights.sbomify.com/CVE-2025-52162/index.md","name":"CVE-2025-52162","record":{"aliases":["GHSA-7h6c-r5x6-jgc8"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Agorum core open","requires_auth":"none","summary":"Attackers can access sensitive data by sending crafted XML input to the RSSReader endpoint in Agorum core open.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"agorum Software GmbH Agorum core open v11.9.2 \u0026 v11.10.1 was discovered to contain an XML External Entity (XXE) via the RSSReader endpoint. This vulnerability allows attackers to access sensitive data via providing a crafted XML input.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"XML external entity in n/a","id":"CVE-2025-52162","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2025-52163"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-52161"},"products":["n/a"],"published":"2025-07-18","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can access sensitive data by sending crafted XML input to the RSSReader endpoint in Agorum core open.","url":"https://insights.sbomify.com/CVE-2025-52162/"}