dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12384

HIGH · 8.6 CVSS v3.1 Published 2025-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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 Document Embedder – Embed PDFs, Word, Excel, and Other Files plugin for WordPress is vulnerable to unauthorized access/modification/loss of data in all versions up to, and including, 2.0.0. This is due to the plugin not properly verifying that a user is authorized to perform an action in the "bplde_save_document_library", "bplde_get_all", "bplde_get_single", and "bplde_delete_document_library" functions. This makes it possible for unauthenticated attackers to create, read, update, and delete arbitrary document_library posts.

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 Document Embedder plugin for WordPress fails to verify user authorization on four AJAX functions (bplde_save_document_library, bplde_get_all, bplde_get_single, bplde_delete_document_library), allowing unauthenticated attackers to create, read, update, and delete arbitrary document_library posts. This is a critical missing capability check enabling complete CRUD operations on sensitive content without any authentication.

MitigationUpdate the plugin to version 2.0.1 or later to receive the vendor patch, or remove the plugin if no update is available. If the plugin must remain unpatched temporarily, disable the affected AJAX endpoints via wp_ajax hooks.

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
Low
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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 Document Embedder plugin is installed
    Navigate to WordPress admin > Plugins and confirm 'Document Embedder' or 'Document Embedder (bplde)' appears in the plugin list, or inspect the wp-content/plugins/ directory for a folder containing 'document-embedder' or 'bplde' in the name
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view the version, or open the main plugin PHP file and read the 'Version' header in the plugin comment block
    Affected if The version is unknown, displayed as lower than 2.0.1, or no version information is visible (unpatched versions lack proper version tracking)
  3. Confirm AJAX endpoints are publicly accessible
    Test unauthenticated access to the AJAX actions by making a GET request to yoursite.com/wp-admin/admin-ajax.php?action=bplde_save_document_library and similarly for actions bplde_get_all, bplde_get_single, and bplde_delete_document_library; a valid JSON response (not a 403/401 error) indicates the endpoints are exposed
    Affected if The AJAX calls return a valid response (even if empty) rather than an authentication/authorization error for unauthenticated requests
  4. Verify the plugin is active on the site
    In WordPress admin > Plugins, confirm the Document Embedder plugin shows as 'Active' under the plugin status
    Affected if The plugin is active and the version is below 2.0.1

If the Document Embedder plugin is installed, active, and the version is below 2.0.1 with unauthenticated AJAX access confirmed, the site is vulnerable to unauthenticated CRUD operations on document_library posts.

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 plugin to version 2.0.1 or later to receive the vendor patch, or remove the plugin if no update is available. If the plugin must remain unpatched temporarily, disable the affected AJAX endpoints via wp_ajax hooks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12384 — 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-12384 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