PYSEC-2025-103
Vulnerability from pysec - Published: 2025-12-18 19:16 - Updated: 2026-05-21 14:54Dify 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.
| Name | purl | dify-client | pkg:pypi/dify-client |
|---|
{
"affected": [
{
"ecosystem_specific": {},
"package": {
"ecosystem": "PyPI",
"name": "dify-client",
"purl": "pkg:pypi/dify-client"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "1.9.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.10",
"0.1.3",
"0.1.4",
"0.1.5",
"0.1.6",
"0.1.7",
"0.1.8"
]
}
],
"aliases": [
"CVE-2025-63387"
],
"details": "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.",
"id": "PYSEC-2025-103",
"modified": "2026-05-21T14:54:25.530161Z",
"published": "2025-12-18T19:16:33.157Z",
"references": [
{
"type": "WEB",
"url": "https://gist.github.com/Cristliu/dfc5f3a31dc6d7fff2754867e5c649a5"
},
{
"type": "ADVISORY",
"url": "https://gist.github.com/Cristliu/cddc0cbbf354de51106ab63a11be94af"
},
{
"type": "REPORT",
"url": "https://github.com/langgenius/dify/discussions"
},
{
"type": "REPORT",
"url": "https://github.com/langgenius/dify/issues/31368#issuecomment-3783712203"
},
{
"type": "FIX",
"url": "https://github.com/langgenius/dify/pull/31392"
},
{
"type": "FIX",
"url": "https://github.com/langgenius/dify/pull/31417"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.