dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-22696

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in WPDeveloper Document Block – Upload & Embed Docs document.This issue affects Document Block – Upload & Embed Docs: from n/a through <= 1.1.0.

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 · moderate confidence

Missing authorization vulnerability in the WordPress Document Block plugin allows authenticated users with limited privileges to access or modify content they should not have permission to access. The CVSS 5.4 score indicates the attacker needs some level of access (likely subscriber or contributor role) but no special privileges.

MitigationUpdate the Document Block – Upload & Embed Docs plugin to version 1.1.1 or later which implements proper capability checks and authorization validation for sensitive operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 the Document Block plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Document Block - Upload & Embed Docs' or 'Document Block' in the plugin list.
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In the Plugins list, click on the plugin name to view its details, or check the plugin header comments in /wp-content/plugins/document-block/includes/document-block.php for the 'Version' defined constant.
    Affected if The version is lower than 1.1.1 (e.g., 1.1.0 or earlier)
  3. Identify low-privilege user roles
    Navigate to Users > All Users in WordPress admin. Review the list for users assigned 'Subscriber' or 'Contributor' roles.
    Affected if Any users with Subscriber or Contributor roles exist on the site
  4. Test document access with limited user
    Log in as a Subscriber or Contributor user. Attempt to access or modify documents via the plugin shortcode or REST API endpoints used by the plugin (e.g., /wp-json/document-block/v1/documents).
    Affected if A low-privilege user can view, upload, or delete documents they did not create

If the Document Block plugin version is below 1.1.1 AND low-privilege users exist on the site, the vulnerability is likely exploitable.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Document Block – Upload & Embed Docs plugin to version 1.1.1 or later which implements proper capability checks and authorization validation for sensitive operations.

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-22696 — 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-22696 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