dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-6380

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ONLYOFFICE Docs WordPress plugin (versions 1.1.0-2.2.0) contains a privilege escalation vulnerability in its oo.callback REST endpoint. The endpoint's permission callback only validates that a provided encrypted attachment ID corresponds to an existing WordPress attachment, but performs no authentication or authorization checks on the requesting user. This allows unauthenticated attackers to authenticate as any existing WordPress user by manipulating the attachment ID parameter.

MitigationUpgrade to version 2.2.1 or later which includes proper authorization checks. If immediate patching is not possible, consider restricting access to the oo.callback endpoint via firewall rules or disabling the ONLYOFFICE plugin until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ONLYOFFICE Docs plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'ONLYOFFICE Docs' or check the wp-content/plugins directory for a folder starting with 'onlyoffice'
    Affected if The plugin is present on the WordPress installation
  2. Check installed plugin version
    In WordPress admin, click on the ONLYOFFICE Docs plugin to view its details, or read the main plugin PHP file for the 'Version' header in the plugin comments
    Affected if Version is 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 2.0.0, 2.1.0, or 2.2.0 (any version from 1.1.0 through 2.2.0 inclusive)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the ONLYOFFICE Docs plugin shows as 'Active'
    Affected if The plugin is currently active and the vulnerable code is executed on requests
  4. Check oo.callback REST endpoint is accessible
    Make a GET request to /wp-json/oo/v1/callback or /?rest_route=/oo/v1/callback and observe if the endpoint responds (it may return an error about missing parameters but confirms the endpoint exists)
    Affected if The endpoint is registered and responds, indicating the vulnerable code path exists

The environment is affected if ONLYOFFICE Docs plugin versions 1.1.0 through 2.2.0 are installed and active, exposing the unauthenticated oo.callback REST endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2.2.1 or later which includes proper authorization checks. If immediate patching is not possible, consider restricting access to the oo.callback endpoint via firewall rules or disabling the ONLYOFFICE plugin until patched.

Recommended fix Moderate confidence

Version 2.2.1 or latest available version

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the ONLYOFFICE Docs plugin
  4. Check if an update is available and apply it
  5. Verify the plugin has been updated to version 2.2.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6380 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data