dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-28951

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/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
Unrestricted Upload of File with Dangerous Type vulnerability in CreedAlly Bulk Featured Image bulk-featured-image allows Upload a Web Shell to a Web Server.This issue affects Bulk Featured Image: from n/a through <= 1.2.4.

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 Bulk Featured Image plugin for WordPress lacks proper file type validation on uploaded files, allowing authenticated attackers to upload arbitrary PHP files (web shells) to the web server. These uploaded files can then be accessed and executed to achieve remote code execution and complete server compromise.

MitigationUpdate the plugin to the latest patched version once released; in the interim, disable the plugin or implement web server-level controls (e.g., .htaccess rules) to prevent PHP execution in upload directories.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Confirm the Bulk Featured Image plugin is installed
    Log in to the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Bulk Featured Image' in the list of active or inactive plugins
    Affected if the plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In the Plugins list, click on the Bulk Featured Image plugin to view its details, or check the plugin header in /wp-content/plugins/bulk-featured-image/ directory via file manager or FTP
    Affected if the version shown is earlier than the latest patched version released for this vulnerability
  3. Verify the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, check whether Bulk Featured Image shows as 'Active' rather than 'Inactive' or 'Must-Use'
    Affected if the plugin status is Active, making the upload functionality accessible
  4. Check for unexpected PHP files in upload directories
    Inspect the /wp-content/uploads/ directory (and any custom upload paths configured in Media Settings) for unfamiliar .php files that were not intentionally uploaded by administrators
    Affected if any .php files exist in upload directories that were not explicitly placed there by trusted users

a user is affected if the Bulk Featured Image plugin is installed, active, and running a version prior to the patched release, or if unknown PHP files are found in upload directories

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 the latest patched version once released; in the interim, disable the plugin or implement web server-level controls (e.g., .htaccess rules) to prevent PHP execution in upload directories.

Recommended fix Moderate confidence

Latest version of Bulk Featured Image plugin (verify fixed version on WordPress repository or vendor site)

  1. Identify the currently installed Bulk Featured Image plugin version in WordPress
  2. Check if the installed version is <= 1.2.4
  3. If vulnerable, check the WordPress plugin repository or CreedAlly for a newer version that addresses this vulnerability
  4. Update the plugin to the latest available version that includes the security fix
  5. Verify the update was successful and the plugin functions correctly
  6. If no fixed version is available from trusted sources, consider alternative plugins or contact the vendor directly for remediation guidance

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
  • 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-28951 — 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-28951 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