# CVE-2025-6380: ONLYOFFICE Docs 1.1.0 - 2.2.0 - Missing Authorization to Unauthenticated Privilege Escalation via callback Function

> Unauthenticated attackers can escalate privileges and log in as arbitrary users via the ONLYOFFICE Docs plugin for WordPress due to missing authorization checks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2025
- **Updated:** 24 Jul 2025
- **Also known as:** GHSA-7rw5-9g4x-gf48

## What is CVE-2025-6380?

CVE-2025-6380 is a critical missing authorization vulnerability in ONLYOFFICE Docs, published on 24 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ONLYOFFICE Docs plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization within its oo.callback REST endpoint in versions 1.1.0 to 2.2.0. The plugin’s permission callback only verifies that the supplied, encrypted attachment ID maps to an existing attachment post, but does not verify the requester’s identity or capabilities. This makes it possible for unauthenticated attackers to log in as an arbitrary user.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-6380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6380 is a critical missing authorization vulnerability in ONLYOFFICE Docs, published on 24 Jul 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-6380 in the wild and no public exploit code.

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

## Sources

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

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