# CVE-2025-43862: Dify Allows Unauthorized Access and Modification of APP Orchestration

> Non-admin users can unauthorizedly access and modify APP orchestration settings in Dify, bypassing intended access controls.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2025
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-6pw4-jqhv-3626

## What is CVE-2025-43862?

CVE-2025-43862 is a high-severity missing authorization vulnerability in langgenius dify, published on 25 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dify is an open-source LLM app development platform. Prior to version 0.6.12, a normal user is able to access and modify APP orchestration, even though the web UI of APP orchestration is not presented for a normal user. This access control flaw allows non-admin users to make unauthorized access and changes on the APPSs. This issue has been patched in version 0.6.12. A workaround for this vulnerability involves updating the the access control mechanisms to enforce stricter user role permissions and implementing role-based access controls (RBAC) to ensure that only users with admin privileges can access Orchestration of the APPs.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Langgenius Dify.

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

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

## Is CVE-2025-43862 being exploited?

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

## Other vulnerabilities in langgenius dify

- [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-43862 and fix it if it is affected.

What it is: CVE-2025-43862 is a high-severity missing authorization vulnerability in langgenius dify, published on 25 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-43862 in the wild and no public exploit code.

Affected product: langgenius dify. 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-43862/ (Markdown: https://insights.sbomify.com/CVE-2025-43862/index.md)
```

## Sources

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

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