# CVE-2025-63387: Missing authorization in n/a > Unauthenticated users can access the system-features endpoint, though maintainers dispute the sensitivity of the exposed data. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 22 Jan 2026 - **Also known as:** GHSA-hrf9-jmwr-6222, PYSEC-2025-103 ## What is CVE-2025-63387? CVE-2025-63387 is a high-severity missing authorization 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 Dify v1.9.1 is vulnerable to Insecure Permissions. An unauthenticated attacker can directly send HTTP GET requests to the /console/api/system-features endpoint without any authentication credentials or session tokens. The endpoint fails to implement proper authorization checks, allowing anonymous access to sensitive system configuration data. NOTE: The maintainer states that the endpoint is unauthenticated by design and serves as a bootstrap mechanism required for the dashboard initialization. They also state that the description inaccurately classifies the returned data as sensitive system configuration, stating that the data is non-sensitive and required for client-side rendering. No PII, credentials, or secrets are exposed. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2025-63387? 1 open source package ship an affected version, including dify-client. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `dify-client` | PyPI | All versions to 1.9.1 | None | Products: Langgenius Dify. ## How do I fix CVE-2025-63387? No fix has been published for CVE-2025-63387 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-63387 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63387 exists. Public exploit code: - Dify v1.9.1 - Broken Access Control (nuclei): http/cves/2025/CVE-2025-63387.yaml ## 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-2025-63388](https://insights.sbomify.com/CVE-2025-63388/): 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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-63387 and fix it if it is affected. What it is: CVE-2025-63387 is a high-severity missing authorization 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63387 exists. Affected packages and fixed versions: - dify-client (PyPI): affected all versions up to 1.9.1; no fix listed 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-63387/ (Markdown: https://insights.sbomify.com/CVE-2025-63387/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63387 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63387 - OSV: https://osv.dev/vulnerability/CVE-2025-63387 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-63387/ Summaries are generated and may contain mistakes; the official description above is the record.