{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6517 exists.","fix":"No fix has been published for CVE-2025-6517 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6517 is a medium-severity server-side request forgery vulnerability in Dromara MaxKey, published on 23 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6517 and fix it if it is affected.\n\nWhat it is: CVE-2025-6517 is a medium-severity server-side request forgery vulnerability in Dromara MaxKey, published on 23 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6517 exists.\n\nAffected product: Dromara MaxKey. 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-6517/ (Markdown: https://insights.sbomify.com/CVE-2025-6517/index.md)","id":"CVE-2025-6517","markdown":"https://insights.sbomify.com/CVE-2025-6517/index.md","name":"CVE-2025-6517","record":{"aliases":["GHSA-j5m6-wqrx-ch36"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MaxKey SSO","requires_auth":"low_privilege","summary":"An attacker with permissions can exploit a server-side request forgery vulnerability in the SAML20 details controller to access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"maxkey","vendor":"maxkey"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A vulnerability was found in Dromara MaxKey up to 4.1.7 and classified as critical. This issue affects the function Add of the file maxkey-webs\\maxkey-web-mgt\\src\\main\\java\\org\\dromara\\maxkey\\web\\apps\\contorller\\SAML20DetailsController.java of the component Meta URL Handler. The manipulation of the argument post leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","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":"Dromara MaxKey Meta URL SAML20DetailsController.java add server-side request forgery","id":"CVE-2025-6517","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"PySpur-Dev pyspur Jinja2 Template single_llm_call.py SingleLLMCallNode special elements used in a template engine","id":"CVE-2025-6518"},"packages":[],"prev":{"headline":"HDF5 H5Fint.c H5F_addr_decode_len heap-based overflow","id":"CVE-2025-6516"},"products":["MaxKey"],"published":"2025-06-23","related":[],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-24","vendors":["Dromara"]},"summary":"An attacker with permissions can exploit a server-side request forgery vulnerability in the SAML20 details controller to access internal resources.","url":"https://insights.sbomify.com/CVE-2025-6517/"}