CVE-2026-1756
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 · uneditedThe WP FOFT Loader plugin for WordPress is vulnerable to arbitrary file uploads due to incorrect file type validation in the 'WP_FOFT_Loader_Mimes::file_and_ext' function in all versions up to, and including, 2.1.39. This makes it possible for authenticated attackers, with Author-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 confidenceThe WP FOFT Loader WordPress plugin versions up to 2.1.39 contains an arbitrary file upload vulnerability in the WP_FOFT_Loader_Mimes::file_and_ext function. The function performs insufficient file type validation, allowing authenticated users with Author-level permissions or higher to upload arbitrary file types including executable scripts. This can lead to remote code execution on the affected WordPress site.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP FOFT Loader plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP FOFT Loader' or check the plugin files in /wp-content/plugins/ for the foft-loader directoryAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin, click on the plugin name in Plugins list to view version details, or open the main plugin PHP file and look for the 'Version' header in the plugin comment blockAffected if Version is 2.1.39 or lower (any version up to and including 2.1.39)
-
Check for the vulnerable function in the codebaseLook for the file /wp-content/plugins/foft-loader/includes/ or similar path containing class-wp-foft-loader-mimes.php; verify the file_and_ext function exists and performs file type validationAffected if The file_and_ext function exists and is used for file uploads
-
Review user accounts with Author-level or higher accessIn WordPress admin, go to Users and review accounts; check which users have Author, Editor, or Administrator rolesAffected if Any untrusted or compromised user accounts exist with Author-level permissions or higher
-
Audit recently uploaded files in the uploads directoryInspect /wp-content/uploads/ and subdirectories for any unexpected file types such as .php, .phtml, .exe, or scripts that were uploaded recentlyAffected if Suspicious executable files are found in the uploads directory
A user is affected if the WP FOFT Loader plugin version is 2.1.39 or lower AND the site has at least one user with Author-level permissions or higher who could exploit the arbitrary file upload vulnerability.
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 version 2.1.40 or later immediately. Additionally, audit existing uploaded files in the uploads directory for any malicious payloads and consider revoking elevated permissions from untrusted users until the update is applied.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1756 — 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-2026-1756 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