dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14633

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 F70 Lead Document Download plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'file_download' function in all versions up to, and including, 1.4.4. This makes it possible for unauthenticated attackers to download any file from the WordPress media library by guessing or enumerating WordPress attachment IDs.

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 F70 Lead Document Download WordPress plugin lacks authorization checks on its file_download function, allowing unauthenticated users to access any file in the WordPress media library by providing attachment IDs. This is a broken access control / Insecure Direct Object Reference (IDOR) vulnerability where the plugin directly uses user-supplied input to retrieve files without verifying user permissions.

MitigationUpdate the plugin to version 1.4.5 or later which includes proper capability checks. If no update is available, disable the plugin or implement interim server-side access controls to restrict file download requests.

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
None
Availability
None

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

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 plugin is installed
    Navigate to WordPress admin > Plugins and locate 'F70 Lead Document Download' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version
    In the Plugins list, click on the plugin to view details, or inspect the plugin header in wp-content/plugins/f70-lead-document-download/f70-lead-document-download.php to find the Version field
    Affected if The version shown is lower than 1.4.5 (e.g., 1.4.4, 1.4.3, 1.0, etc.)
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify the plugin shows as 'Active' under the plugin status
    Affected if The plugin is active and the version is below 1.4.5
  4. Identify vulnerable endpoint exposure
    Check if the plugin registers a shortcode or AJAX action linked to the file_download function - inspect the plugin main file for add_action calls referencing 'file_download' or 'wp_ajax_f70_download'
    Affected if The plugin registers download-related actions accessible to unauthenticated users and the version is below 1.4.5

The environment is affected if the F70 Lead Document Download plugin is installed, active, and running a version lower than 1.4.5, allowing any visitor to download arbitrary media library files by supplying attachment IDs.

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

Update the plugin to version 1.4.5 or later which includes proper capability checks. If no update is available, disable the plugin or implement interim server-side access controls to restrict file download requests.

Recommended fix Moderate confidence

1.4.5 or later

  1. Check the WordPress admin dashboard for plugin updates for F70 Lead Document Download
  2. If an update is available, update to the latest version
  3. Verify the update resolves the unauthorized file download vulnerability
  4. Ensure WordPress core and all other plugins are also updated

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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