CVE-2025-58819
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 · uneditedUnrestricted 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 confidenceThe CreedAlly Bulk Featured Image WordPress plugin has an unrestricted file upload vulnerability allowing attackers to upload dangerous file types (web shells) directly to the web server, potentially achieving remote code execution. The plugin fails to validate file types before accepting uploads.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Bulk Featured Image plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Bulk Featured Image'. Note the installed version from the plugin description.Affected if The plugin is installed and the version falls within any vulnerable version range (compare your installed version against the affected versions once known).
-
Locate the plugin upload directoryCheck the plugin settings page in WordPress admin for upload path configuration, or inspect the plugin code for the upload_dir filter to identify where files are stored.Affected if Uploads are stored in a publicly accessible web directory (within /wp-content/uploads/ or similar web-accessible paths).
-
Verify upload directory is web-accessibleCheck the web server configuration or .htaccess rules to confirm the upload directory can be accessed via HTTP/HTTPS.Affected if The directory storing uploaded files is directly accessible via web browser without authentication.
-
Confirm script execution is allowed in upload directoryCheck if the upload directory lacks restrictions on executing PHP files - look for .htaccess rules or server config that would block PHP execution, or attempt to access a test PHP file in the upload path via browser.Affected if PHP files stored in the upload directory can be executed directly by the web server (no execution blocking is in place).
You are affected if the Bulk Featured Image plugin is installed AND uploads are stored in a web-accessible directory where PHP script execution is not blocked.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest version immediately. If no patch is available, remove the plugin and implement server-level restrictions (disable PHP execution in upload directories, use .htaccess rules to block script uploads).
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58819 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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