CVE-2025-63388: Critical severity Dify dify vulnerability

Published Dec 18, 2025
·
Updated

A Cross-Origin Resource Sharing (CORS) misconfiguration vulnerability exists in Dify v1.9.1 in the /console/api/system-features endpoint. The endpoint implements an overly permissive CORS policy that reflects arbitrary Origin headers and sets Access-Control-Allow-Credentials: true, allowing any external domain to make authenticated cross-origin requests. NOTE: the Supplier disputes this, providing the rationale of "sending requests with credentials does not provide any additional access compared to unauthenticated requests."

Affected Software

2 affected components
Dify dify
LangGenius Dify Node.js=1.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update the CORS configuration for /console/api/system-features to stop reflecting arbitrary Origin values and avoid allowing authenticated cross-origin requests by setting Access-Control-Allow-Credentials to false (or only enabling it for explicitly allowlisted origins).

    Dify (/console/api/system-features endpoint) CORS policy (Access-Control-Allow-Origin and Access-Control-Allow-Credentials) = Do not reflect arbitrary Origin headers; set Access-Control-Allow-Credentials to false or only allow specific trusted origins
  2. Operational

    After changing the CORS policy, test the /console/api/system-features endpoint to confirm that requests from untrusted external origins are rejected and that authenticated cross-origin requests are no longer permitted.

Event History

Dec 18, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-63388?

CVE-2025-63388 is considered a high-severity vulnerability due to the potential for abuse of the vulnerable CORS policy.

2

How do I fix CVE-2025-63388?

To fix CVE-2025-63388, configure the CORS policy to restrict the allowed origins and ensure Access-Control-Allow-Credentials is set to false.

3

Which versions of Dify are affected by CVE-2025-63388?

Dify version 1.9.1 is affected by CVE-2025-63388 due to its misconfigured CORS policy.

4

What type of vulnerability is CVE-2025-63388?

CVE-2025-63388 is a Cross-Origin Resource Sharing (CORS) misconfiguration vulnerability.

5

What are the risks associated with CVE-2025-63388?

The risks associated with CVE-2025-63388 include unauthorized access to sensitive data and the potential for cross-origin attacks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203