dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10580

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Hustle – Email Marketing, Lead Generation, Optins, Popups plugin for WordPress is vulnerable to unauthorized form submissions due to a missing capability check on the submit_form() function in all versions up to, and including, 7.8.5. This makes it possible for unauthenticated attackers to submit unpublished forms.

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 has an authorization bypass vulnerability in the submit_form() function which lacks a capability check. This allows unauthenticated attackers to submit unpublished forms by directly invoking the function without proper authorization validation.

MitigationUpdate the plugin to version 7.8.6 or later which includes proper capability checks on the submit_form() function to ensure only authorized users can submit forms.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 Hustle plugin is installed
    Check for the Hustle plugin directory at wp-content/plugins/hustle/ and list its files, or look for 'Hustle' in the WordPress plugins admin panel
    Affected if The Hustle plugin is present and active in the WordPress installation
  2. Determine installed Hustle version
    Open the main plugin file (typically hustle.php) and locate the Version header in the plugin comment block, or check the version in readme.txt
    Affected if The installed version is lower than 7.8.6 (versions prior to 7.8.6 lack the capability check)
  3. Check for unpublished forms
    Query the WordPress database for Hustle forms with post_status not equal to 'publish', or inspect forms in the Hustle admin panel under the Forms section
    Affected if There are unpublished (draft, pending, or private) forms that could be submitted via the vulnerable function
  4. Verify exposed AJAX or endpoint access
    Inspect the plugin code for AJAX action hooks registering 'submit_form' function (search for 'wp_ajax_hustle_submit_form' or 'wp_ajax_nopriv_hustle_submit_form' in the plugin files)
    Affected if The plugin registers an AJAX endpoint accessible to unauthenticated users (nopriv) for the submit_form function

A user is affected if the Hustle plugin is installed with a version below 7.8.6 and has unpublished forms that could be submitted without authentication due to missing capability checks on the submit_form() function.

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 version 7.8.6 or later which includes proper capability checks on the submit_form() function to ensure only authorized users can submit forms.

Recommended fix Moderate confidence

7.8.6 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Hustle – Email Marketing, Lead Generation, Optins, Popups'
  4. If an update is available, click 'Update Now'
  5. Alternatively, download the latest version from wordpress.org/plugins/hustle/ and upload via Plugins > Add New > Upload Plugin
  6. After update, verify the plugin version is higher than 7.8.5

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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