dbcve.org
Multi Step FormWordPress extension · Mondula

CVE-2024-50428

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to 1.7.22 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in mondula2016 Multi Step Form multi-step-form allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Multi Step Form: from n/a through <= 1.7.21.

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 · moderate confidence

A Missing Authorization vulnerability in the mondula2016 Multi Step Form WordPress plugin allows unauthenticated or unauthorized users to exploit incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to sensitive functionality or data, potentially giving attackers complete access to form configurations and submissions.

MitigationApply the latest vendor patch when available; until then, restrict access to the plugin endpoints at the web server level or consider disabling the plugin if the risk is unacceptable. After patching, verify all user roles cannot bypass access controls.

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
Multi Step FormWordPress extension
Affected:< 1.7.22

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 plugin installation and version
    Navigate to WordPress admin > Plugins, find 'Mondula Multi Step Form' (or 'Multi Step Form'), and note the version number. Alternatively, inspect the plugin file at /wp-content/plugins/multi-step-form/multi-step-form.php and check the Version header in the plugin comments.
    Affected if The installed version is lower than 1.7.22 or the version cannot be determined (plugin is present but unversioned).
  2. Verify plugin is active
    In WordPress admin > Plugins, confirm the plugin status shows as 'Active'. An inactive plugin with this vulnerability poses less immediate risk.
    Affected if The plugin is active and version is below 1.7.22.
  3. Test unauthenticated endpoint access
    Use a browser or curl to request common plugin endpoints without logging in, such as: curl -s -o /dev/null -w '%{http_code}' https://yourdomain.com/wp-admin/admin-ajax.php?action=msf_ajax_handler (or similar AJAX actions the plugin registers). Check for HTTP 200 responses that return data rather than 403/401.
    Affected if Requests return 200 status with form data, configurations, or submissions without requiring login credentials.
  4. Inspect plugin capabilities configuration
    If you have admin access, go to the plugin settings page (usually under 'Multi Step Form' in the admin menu) and examine any access control, security level, or permission settings. Look for options controlling who can view/edit forms.
    Affected if There is no visible authorization setting, or the setting defaults to allowing any visitor (public/guest) access to form data.

If the Mondula Multi Step Form plugin is active at a version below 1.7.22 and its endpoints are accessible without authentication (HTTP 200 responses), the environment is affected by this missing authorization vulnerability.

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 1.7.22 or later
Fixed in 1.7.22
Interim mitigation

Apply the latest vendor patch when available; until then, restrict access to the plugin endpoints at the web server level or consider disabling the plugin if the risk is unacceptable. After patching, verify all user roles cannot bypass access controls.

Recommended fix High confidence

1.7.22

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Multi Step Form plugin in the list
  4. Click 'Update now' if an update is available, or manually upload version 1.7.22 from the WordPress plugin repository
  5. Verify the plugin is running version 1.7.22 or higher after updating
  6. Test that form functionality and admin access controls work correctly

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

Fix this in Multi Step Form Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,170
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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