{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56520 exists.","fix":"No fix has been published for CVE-2025-56520 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56520 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Sep 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-56520 and fix it if it is affected.\n\nWhat it is: CVE-2025-56520 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Sep 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-56520 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-56520/ (Markdown: https://insights.sbomify.com/CVE-2025-56520/index.md)","id":"CVE-2025-56520","markdown":"https://insights.sbomify.com/CVE-2025-56520/index.md","name":"CVE-2025-56520","record":{"aliases":["GHSA-x284-mqwh-m8wm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Dify AI platform","requires_auth":"none","summary":"An attacker can exploit an SSRF vulnerability in Dify's remote file upload API to access internal resources or bypass security controls.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dify","vendor":"dify"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Dify v1.6.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component controllers.console.remote_files.RemoteFileUploadApi. A different vulnerability than CVE-2025-29720.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-56520.yaml","stars":null,"title":"Dify v1.6.0 - Server-Side Request Forgery"}],"tier":"weaponised"},"has_fix":false,"headline":"Server-side request forgery in n/a","id":"CVE-2025-56520","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-56526"},"packages":[],"prev":{"headline":"Fiora chat group avatar is vulnerable to XSS via SVG files","id":"CVE-2025-56515"},"products":["n/a"],"published":"2025-09-30","related":[{"cvss_score":9.3,"headline":"Dify \u003c 1.14.2 Authorization Bypass via Trace Configuration Endpoints","id":"CVE-2026-41947","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":9.3,"headline":"Dify v1.14.1 Path Traversal via Plugin Daemon Internal API Access","id":"CVE-2026-41948","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":8.8,"headline":"Pandas Query Injection in langgenius/dify","id":"CVE-2025-0185","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.7,"headline":"Dify \u003c 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text","id":"CVE-2026-61461","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":8.4,"headline":"Dify Vulnerable to Plaintext API Key Exposure via Model Provider Configuration Endpoint","id":"CVE-2025-67732","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":8.2,"headline":"Dify \u003c 1.14.2 Authorization Bypass via File Preview Endpoint","id":"CVE-2026-41949","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":6.5,"headline":"Server-Side Request Forgery (SSRF) in langgenius/dify","id":"CVE-2024-11822","kev_date_added":null,"published":"2025-03-20"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-01","vendors":["n/a"]},"summary":"An attacker can exploit an SSRF vulnerability in Dify's remote file upload API to access internal resources or bypass security controls.","url":"https://insights.sbomify.com/CVE-2025-56520/"}