Unrestricted File UploadWeakness · CWE-434

CVE-2026-28114

CRITICAL · 9.1 CVSS v3.1 Published 2026-03-05
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 firassaidi WooCommerce License Manager fs-license-manager allows Upload a Web Shell to a Web Server.This issue affects WooCommerce License Manager: from n/a through <= 7.0.6.

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

Unrestricted file upload vulnerability in WooCommerce License Manager plugin allows unauthenticated attackers to upload arbitrary PHP files (web shells) to the web server, enabling remote code execution. The plugin lacks proper file type validation and access controls on upload functionality.

MitigationImmediately upgrade to a patched version of WooCommerce License Manager beyond 7.0.6. If no patch is available, disable the plugin or implement web server-level restrictions to block PHP file uploads in the uploads directory.

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. Identify if WooCommerce License Manager is installed
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'woocommerce-license-manager' or 'license-manager-for-woocommerce', or query the WordPress database: SELECT plugin FROM wp_options WHERE option_name = 'active_plugins' LIKE '%license%';
    Affected if The plugin folder exists in plugins directory or the plugin is listed in active WordPress plugins
  2. Determine the installed plugin version
    Check the main plugin file (usually license-manager.php or class-license-manager.php) for the 'Version' header, or look in WordPress admin under Plugins > Installed Plugins
    Affected if Version is 7.0.6 or lower (the vulnerability affects versions up to and including 7.0.6)
  3. Inspect the uploads directory for suspicious files
    Check wp-content/uploads/ and subdirectories for .php files using: find /path/to/wp-content/uploads -name '*.php' -type f
    Affected if Any unexpected PHP files are found in the uploads directory, especially with random or suspicious names (e.g., shell.php, backdoor.php)
  4. Review access controls on upload endpoints
    Examine the plugin source code for the upload handler function - look for files like class-ajax.php or class-upload.php and verify if there is nonce verification or capability checks before processing uploads
    Affected if The upload functionality lacks nonce verification, capability checks, or file type validation (no restriction on .php files)
  5. Check web server access logs for upload attempts
    Review Apache/Nginx access logs for POST requests to the plugin's upload endpoint (search for requests to /wp-admin/admin-ajax.php?action=lm_upload or similar)
    Affected if Unauthenticated POST requests to upload endpoints are present in logs, especially those containing suspicious filenames

A user is affected if WooCommerce License Manager version 7.0.6 or lower is installed and the upload functionality is exposed without proper restrictions, or if suspicious PHP 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade to a patched version of WooCommerce License Manager beyond 7.0.6. If no patch is available, disable the plugin or implement web server-level restrictions to block PHP file uploads in the uploads directory.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28114 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