dbcve.org
WebinarignitionWordPress extension · Saleswonder

CVE-2024-32445

HIGH · 8.8 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to 3.06.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Saleswonder Team: Tobias WebinarIgnition webinar-ignition.This issue affects WebinarIgnition: from n/a through <= 3.05.8.

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

This is a Cross-Site Request Forgery (CSRF) vulnerability in the WebinarIgnition WordPress plugin (version <= 3.05.8). The plugin lacks proper anti-CSRF tokens or origin validation on state-changing operations, allowing authenticated administrators to be tricked into executing unintended actions such as modifying plugin settings, creating/deleting webinars, or changing user roles.

MitigationUpdate to a patched version of WebinarIgnition if available. If no patch exists, implement anti-CSRF tokens (nonces) on all POST/PUT/DELETE endpoints and verify the request origin server-side using referer header checks or same-origin validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebinarignitionWordPress extension
Affected:< 3.06.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify the installed WebinarIgnition plugin version
    Log into WordPress admin and navigate to Plugins > WebinarIgnition, or inspect the plugin main file (usually webinarignition.php) in wp-content/plugins/ and locate the 'Version' header in the plugin comments.
    Affected if The installed version is less than 3.06.0 (the vulnerable version range is <= 3.05.8, and patched in 3.06.0).
  2. Verify presence of nonce fields in admin forms
    Access the WebinarIgnition plugin admin pages (Create Webinar, Settings, etc.) and view the page source (right-click > View Page Source). Search for input fields with type='hidden' and name containing 'nonce', '_wpnonce', or 'security'.
    Affected if No nonce fields are found in state-changing forms (e.g., forms that save settings, create/delete webinars, or modify user roles).
  3. Inspect plugin PHP files for nonce verification
    Locate the main plugin PHP files in wp-content/plugins/webinarignition/. Search within these files for functions wp_verify_nonce, check_admin_referer, check_ajax_referer, or wp_create_nonce.
    Affected if The plugin code does not contain calls to nonce verification functions, indicating missing CSRF protection.
  4. Check for origin/referer validation in AJAX actions
    Examine the plugin's AJAX handlers (look for add_action('wp_ajax_') hooks) in the main plugin file or includes. Verify if $_SERVER['HTTP_REFERER'] or origin header validation is performed before executing state-changing operations.
    Affected if No server-side origin or referer validation is found in the AJAX action handlers.

If the installed WebinarIgnition version is below 3.06.0 AND no nonce fields or verification logic are present in the plugin admin pages and PHP code, the environment is vulnerable to CVE-2024-32445.

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
Upgrade available Upgrade to 3.06.0 or later
Fixed in 3.06.0
Interim mitigation

Update to a patched version of WebinarIgnition if available. If no patch exists, implement anti-CSRF tokens (nonces) on all POST/PUT/DELETE endpoints and verify the request origin server-side using referer header checks or same-origin validation.

Recommended fix High confidence

3.06.0

  1. Backup your WordPress website database and files before proceeding with any updates
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate WebinarIgnition in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 3.06.0 or later
  5. Verify the plugin update completed successfully by checking the installed version
  6. Test that WebinarIgnition functionality works correctly after the update

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

Fix this in Webinarignition Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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