# CVE-2025-63388: Misconfiguration in n/a

> An overly permissive CORS policy in Dify allows external domains to make authenticated cross-origin requests, potentially exposing sensitive data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 28 Jan 2026
- **Also known as:** GHSA-96g3-r54f-fx2v

## What is CVE-2025-63388?

CVE-2025-63388 is a critical vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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."

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2025-63388?

It affects 1 product.


Products: Langgenius Dify.

## How do I fix CVE-2025-63388?

No fix has been published for CVE-2025-63388 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63388 being exploited?

There is no known exploitation of CVE-2025-63388 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-56157](https://insights.sbomify.com/CVE-2025-56157/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-3466](https://insights.sbomify.com/CVE-2025-3466/): Unsanitized Input in langgenius/dify (critical 9.8)
- [CVE-2025-63386](https://insights.sbomify.com/CVE-2025-63386/): Misconfiguration in n/a (critical 9.1)
- [CVE-2024-10252](https://insights.sbomify.com/CVE-2024-10252/): Code Injection in langgenius/dify (high 8.8)
- [CVE-2024-12776](https://insights.sbomify.com/CVE-2024-12776/): Authentication Bypass in langgenius/dify (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63388 and fix it if it is affected.

What it is: CVE-2025-63388 is a critical vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63388 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63388/ (Markdown: https://insights.sbomify.com/CVE-2025-63388/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63388
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63388
- OSV: https://osv.dev/vulnerability/CVE-2025-63388

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63388/
Summaries are generated and may contain mistakes; the official description above is the record.