dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-1405

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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 Slider Future plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'slider_future_handle_image_upload' function in all versions up to, and including, 1.0.5. This makes it possible for unauthenticated attackers 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 Slider Future WordPress plugin has an unauthenticated arbitrary file upload vulnerability in the slider_future_handle_image_upload function. The function fails to validate file types, allowing attackers to upload any file type to the server. Since uploaded files are accessible via web, this enables remote code execution.

MitigationUpdate the plugin to the latest version if available. If no patch exists, disable the plugin immediately and consider web application firewall rules to block malicious upload 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Slider Future plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'slider-future' or similar, and confirm the plugin files exist.
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    Open the main plugin PHP file (usually slider-future.php or similar in the plugin folder) and locate the plugin version header comment (e.g., 'Version: x.x.x'). Compare this version to the latest available version from the WordPress plugin repository.
    Affected if The installed version lacks the security fix for arbitrary file upload
  3. Check for exposed upload endpoint
    Search the plugin source code for 'slider_future_handle_image_upload' function and identify if it's hooked to an unauthenticated WordPress AJAX action (admin-ajax.php) or other accessible endpoint. Test by examining if the action is registered without a capability check or login requirement.
    Affected if The upload function is accessible without authentication (no current_user_auth check found)
  4. Inspect wp-content/uploads directory
    Check the WordPress uploads folder (wp-content/uploads/) for any PHP files or other executable file types that should not be present. Use file system listing: ls -la wp-content/uploads/ and look for suspicious extensions.
    Affected if Unexpected PHP files or other executable scripts are found in the uploads directory

The environment is affected if the Slider Future plugin is installed and the vulnerable upload function is accessible without authentication, or if suspicious files exist in the uploads directory.

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 version if available. If no patch exists, disable the plugin immediately and consider web application firewall rules to block malicious upload requests.

Recommended fix Moderate confidence

Slider Future plugin version 1.0.6 or later

  1. Check the current installed version of the Slider Future plugin in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload Plugin (or check WordPress plugin repository) to verify if version 1.0.6 or later is available
  3. If version 1.0.6 or later is available, update the plugin directly through WordPress admin: Plugins > Slider Future > Update Now
  4. If automatic update is not available, manually upload the updated plugin ZIP file through Plugins > Add New > Upload Plugin
  5. After update, verify the new version is installed under Plugins > Installed Plugins
  6. Ensure the slider_future_handle_image_upload function now properly validates file types before allowing uploads
Caveat Review plugin settings after upgrade as any functionality changes in 1.0.6 should be verified

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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