dbcve.org
ForminatorWordPress extension · Incsub

CVE-2024-31077

HIGH · 7.2 CVSS v3.1 Published 2024-04-23
Fix available
A fix is available. Upgrade to 1.29.3 or later.
See remediation →
78/100
Remediation priority · High
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
Forminator prior to 1.29.3 contains a SQL injection vulnerability. If this vulnerability is exploited, a remote authenticated attacker with an administrative privilege may obtain and alter any information in the database and cause a denial-of-service (DoS) condition.

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

Forminator plugin for WordPress prior to version 1.29.3 contains a SQL injection vulnerability. The flaw allows a remote authenticated attacker with administrative privileges to inject malicious SQL queries, potentially enabling unauthorized access to, modification of, or deletion of arbitrary database records, as well as causing denial-of-service conditions.

MitigationUpgrade Forminator to version 1.29.3 or later to apply the vendor patch. If immediate upgrading is not feasible, restrict administrative access to trusted users and monitor database queries for suspicious activity.

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
ForminatorWordPress extension
Affected:< 1.29.3

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify Forminator plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Forminator' in the list, or check the /wp-content/plugins/forminator directory exists on the server
    Affected if Forminator plugin is present on the WordPress site
  2. Check installed Forminator version
    In WordPress admin, go to Plugins > Installed Plugins > Forminator and read the version number displayed below the plugin name, or check the version in the plugin's main PHP file header
    Affected if Version is present and less than 1.29.3
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify Forminator shows 'Active' status, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';
    Affected if Forminator is active and version is below 1.29.3
  4. Identify administrative users
    In WordPress admin, go to Users > All Users and review accounts with Administrator role, or query: SELECT user_login, user_email FROM wp_users WHERE ID IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%');
    Affected if Any administrative users exist on the site with Forminator < 1.29.3 active

The site is affected if Forminator plugin is installed, active, and the installed version is below 1.29.3.

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.29.3 or later
Fixed in 1.29.3
Interim mitigation

Upgrade Forminator to version 1.29.3 or later to apply the vendor patch. If immediate upgrading is not feasible, restrict administrative access to trusted users and monitor database queries for suspicious activity.

Recommended fix High confidence

Forminator 1.29.3 or later

  1. Backup your WordPress database and files before making any changes
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find Forminator in the plugin list
  5. Click 'Update now' if an update is available, or manually upload Forminator version 1.29.3 or later
  6. Verify the updated version is 1.29.3 or higher
  7. Test that forms, polls, and quizzes function correctly after the update
Caveat Standard plugin update precautions apply; test in staging if available

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

Fix this in Forminator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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