dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-10647

HIGH · 8.8 CVSS v3.1 Published 2025-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The Embed PDF for WPForms plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ajax_handler_download_pdf_media function in all versions up to, and including, 1.1.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Embed PDF for WPForms plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ajax_handler_download_pdf_media function. Authenticated users with Subscriber-level access can upload arbitrary files, potentially achieving remote code execution.

MitigationUpdate the plugin to version 1.1.6 or later where proper file type validation has been implemented, or remove the plugin if no update is available.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Embed PDF for WPForms' or check the plugin files in /wp-content/plugins/ directory for the presence of a folder containing 'embed-pdf-for-wpforms' or similar
    Affected if The plugin is installed and active
  2. Check installed version
    In WordPress admin_plugins page, find the plugin and note the version number displayed, or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if Version is lower than 1.1.6 (versions prior to 1.1.6 lack proper file type validation)
  3. Confirm ajax endpoint is accessible
    Check if the WordPress site has the ajax_handler_download_pdf_media function exposed by accessing /wp-admin/admin-ajax.php?action=download_pdf_media or reviewing the plugin source code for the add_action('wp_ajax_download_pdf_media') or wp_ajax_nopriv_ hook
    Affected if The ajax endpoint is registered and accessible without additional authorization checks (the vulnerability exists when this endpoint accepts file uploads without proper validation)
  4. Verify subscriber-level access
    In WordPress admin, go to Users > Roles and confirm the Subscriber role exists, or check if any user with Subscriber role can access wp-admin/admin-ajax.php to trigger the vulnerable function
    Affected if Users with Subscriber-level access can make authenticated requests to the site (WordPress default configuration allows subscribers to authenticate)
  5. Identify upload capability exposure
    Review the plugin code for the ajax_handler_download_pdf_media function to see if it accepts file uploads and lacks file type validation (look for $_FILES handling without wp_check_filetype or similar validation)
    Affected if The function accepts file uploads from user input without validating file type against allowed types (the vulnerability is present when arbitrary file extensions can be passed)

You are affected if the Embed PDF for WPForms plugin is installed with a version lower than 1.1.6 and the ajax_handler_download_pdf_media function accepts unauthenticated or subscriber-level file uploads without proper file type validation.

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 1.1.6 or later where proper file type validation has been implemented, or remove the plugin if no update is available.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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