dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-0911

HIGH · 7.5 CVSS v3.1 Published 2026-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
The Hustle – Email Marketing, Lead Generation, Optins, Popups plugin for WordPress is vulnerable to arbitrary file uploads due to incorrect file type validation in the action_import_module() function in all versions up to, and including, 7.8.9.2. This makes it possible for authenticated attackers, with a lower-privileged role (e.g., Subscriber-level access and above), to upload arbitrary files on the affected site's server which may make remote code execution possible. Successful exploitation requires an admin to grant Hustle module permissions (or module edit access) to the low-privileged user so they can access the Hustle admin page and obtain the required nonce.

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 Hustle WordPress plugin versions up to 7.8.9.2 contain an arbitrary file upload vulnerability in the action_import_module() function. The plugin fails to properly validate file types during module import, allowing authenticated users with Subscriber-level access (or higher) to upload arbitrary files when an administrator has granted them Hustle module permissions. This can lead to remote code execution.

MitigationUpdate the Hustle plugin to the latest version once available, or restrict Hustle module permissions to prevent low-privileged users from accessing the import functionality until a patch is released.

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

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Hustle plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate Hustle (or check wp-content/plugins/ for hustle directory). Note the version number displayed.
    Affected if Hustle plugin is installed and version is 7.8.9.2 or earlier (any version up to 7.8.9.2)
  2. Verify user role and Hustle permissions
    Go to Users > All Users in WordPress admin. For each user with Subscriber role or higher, check if they have been granted Hustle module permissions (usually found under Hustle > Settings > Access, or in user profile capabilities).
    Affected if Any user with Subscriber-level access or higher has Hustle module import permissions granted by an administrator
  3. Check if import functionality is accessible
    Attempt to access the module import feature: navigate to Hustle > All Modules, or check if a menu item for importing modules exists. The vulnerable function is action_import_module() in the plugin.
    Affected if The Hustle import module feature is present and accessible to the authenticated user
  4. Review uploaded files directory
    If accessible, check wp-content/uploads/hustle/ or similar upload directories for any unexpected file types (PHP files, scripts) that were not intended to be uploaded.
    Affected if Unexpected file types exist in Hustle upload directories that were not explicitly allowed

You are affected if the Hustle plugin version is 7.8.9.2 or earlier AND any authenticated user with Subscriber-level access or higher has been granted Hustle module import permissions by an administrator.

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 Hustle plugin to the latest version once available, or restrict Hustle module permissions to prevent low-privileged users from accessing the import functionality until a patch is released.

Recommended fix High confidence

7.8.9.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Hustle – Email Marketing, Lead Generation, Optins, Popups' plugin
  4. If an update is available, click 'Update Now' to upgrade to version 7.8.9.3 or later
  5. Alternatively, use WP-CLI: wp plugin update hustle
  6. After updating, verify the new version is 7.8.9.3 or higher under Plugins > Installed Plugins
  7. Review user roles and permissions to ensure only trusted users have Hustle module edit access

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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