dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-4410

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 IgnitionDeck Crowdfunding Platform plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.9.8. This is due to missing capability checks on various functions called via AJAX actions in the ~/classes/class-idf-wizard.php file. This makes it possible for authenticated attackers, with subscriber access or higher, to execute various AJAX actions. This includes actions to change the permalink structure, plugin settings and others.

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 IgnitionDeck Crowdfunding Platform plugin for WordPress versions up to 1.9.8 lack capability checks on AJAX action handlers in class-idf-wizard.php, allowing any authenticated user with subscriber-level access or higher to invoke privileged functions that modify plugin settings and permalink structures.

MitigationUpdate to version 1.9.9 or later which implements proper authorization checks, or manually add current_user_can() capability verification to all AJAX handlers in the affected file.

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

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

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 IgnitionDeck plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'IgnitionDeck Crowdfunding Platform' and note the version number displayed. Alternatively, check the plugin's main PHP file header or version.php for the version constant.
    Affected if The plugin is installed and the version displayed is 1.9.8 or earlier (any version up to and including 1.9.8 is vulnerable).
  2. Locate the affected AJAX handler file
    Access the WordPress site filesystem via file manager or FTP, navigate to wp-content/plugins/ignitiondeck/ and locate class-idf-wizard.php.
    Affected if The file class-idf-wizard.php exists in the plugin directory.
  3. Verify AJAX handlers lack capability checks
    Open class-idf-wizard.php in a text editor and search for AJAX action hooks (add_action('wp_ajax_...')) or functions handling AJAX requests. Examine each handler to see if it includes a current_user_can() or similar capability verification call before performing privileged operations.
    Affected if Any AJAX handler in this file processes requests without first verifying the user has appropriate capabilities (e.g., manage_options, manage_settings).
  4. Confirm user role accessibility
    In WordPress admin, go to Users > Users List to confirm whether subscriber-level or higher user accounts exist. In a default WordPress installation, the 'Subscriber' role is the lowest privilege level.
    Affected if There are user accounts with Subscriber, Contributor, Author, or Editor roles who can access the WordPress dashboard.

A user is affected if the IgnitionDeck plugin version is 1.9.8 or earlier, the class-idf-wizard.php file exists, and any authenticated user with Subscriber-level access or higher can trigger AJAX actions without capability validation.

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 to version 1.9.9 or later which implements proper authorization checks, or manually add current_user_can() capability verification to all AJAX handlers in the affected file.

Recommended fix Moderate confidence

Version 1.9.9 or later (check WordPress plugin repository for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the IgnitionDeck Crowdfunding Platform plugin
  4. Check if a newer version is available by clicking 'View version details' or checking the plugin page
  5. If version 1.9.9 or later is available, click 'Update Now' to install the patched version
  6. After updating, verify the plugin is functioning correctly by testing frontend crowdfunding features
  7. Review user roles and permissions to ensure only trusted users have subscriber-level access or higher
Caveat Review plugin settings after upgrade as minor configuration changes may occur with version updates

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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