dbcve.org
Metform Elementor Contact Form BuilderWordPress extension · Wpmet

CVE-2024-33570

HIGH · 8.8 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 3.8.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Roxnor Metform metform.This issue affects Metform: from n/a through <= 3.8.3.

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

Missing Authorization vulnerability in Metform WordPress plugin (versions <= 3.8.3) allows unauthenticated or low-privileged attackers to access functionality or data they should not be able to reach, potentially leading to unauthorized form data access or configuration changes.

MitigationUpdate Metform to the latest version when available, or implement proper authorization checks on all sensitive endpoints and actions within the plugin.

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
Metform Elementor Contact Form BuilderWordPress extension
Affected:< 3.8.4

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

CVSS:3.1/AV:N/AC:L/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 Metform plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Metform Elementor Contact Form Builder' or check the plugin files in /wp-content/plugins/ for metform directory
    Affected if Metform plugin is present in the WordPress installation
  2. Check installed Metform version
    Go to WordPress admin > Plugins > Installed Plugins > Metform and read the version number displayed, or check version in plugin's main PHP file header
    Affected if The installed version is 3.8.3 or lower (versions before 3.8.4)
  3. Identify sensitive form data access points
    Review WordPress roles and capabilities assigned to low-privileged users (subscriber, contributor) and test whether they can access form submission data via Metform endpoints or admin pages they should not normally access
    Affected if Low-privileged users can view, modify, or export form submissions or configuration data they are not authorized to access
  4. Audit Metform endpoint accessibility
    Use a browser or HTTP tool to access Metform-related URLs (such as admin-ajax.php endpoints or plugin-specific REST API routes) while logged in as a low-privileged user or logged out, checking if sensitive operations are reachable without proper authorization
    Affected if Sensitive plugin functionality is accessible without authentication or to users lacking proper capabilities

You are affected if the Metform plugin is installed with version 3.8.3 or lower and sensitive form data or configuration endpoints are accessible to unauthenticated users or low-privileged accounts.

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.8.4 or later
Fixed in 3.8.4
Interim mitigation

Update Metform to the latest version when available, or implement proper authorization checks on all sensitive endpoints and actions within the plugin.

Recommended fix High confidence

3.8.4

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to WordPress dashboard > Plugins.
  3. 3. Locate the Metform Elementor Contact Form Builder plugin.
  4. 4. Check the current installed version to confirm it is 3.8.3 or earlier.
  5. 5. Update the plugin to version 3.8.4 or later.
  6. 6. Verify the update was successful by checking the installed version number.
  7. 7. Test form submissions and related functionality to ensure the plugin continues to work correctly after the update.

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

Fix this in Metform Elementor Contact Form Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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