dbcve.org
Formidable FormsWordPress extension · Strategy11

CVE-2024-6725

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-31
Fix available
A fix is available. Upgrade to 6.11.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘html’ parameter in all versions up to, and including, 6.11.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with form editing permissions and Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Formidable Forms WordPress plugin is vulnerable to stored Cross-Site Scripting (XSS) via the 'html' parameter due to insufficient input sanitization and output escaping. Authenticated attackers with form editing permissions (Subscriber-level and above) can inject arbitrary JavaScript that executes whenever users access affected pages. The vulnerability exists in all versions up to and including 6.11.1.

MitigationUpdate to version 6.11.2 or later which contains the fix for proper input sanitization and output escaping. Additionally, review and restrict form editing permissions to minimize the attack surface for lower-privileged users.

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
Formidable FormsWordPress extension
Affected:< 6.11.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Formidable Forms plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and locate 'Formidable Forms' in the list
    Affected if The Formidable Forms plugin appears in the installed plugins list
  2. Check installed plugin version
    In the Plugins list, look at the version number displayed beneath the 'Formidable Forms' plugin name, or check the plugin's main PHP file header for the Version field
    Affected if The version listed is earlier than 6.11.2 (e.g., 6.11.1, 6.10.x, etc.)
  3. Identify forms using the html field
    Go to Formidable > Forms and inspect each form. Edit each form and look in the field builder for any field with type 'HTML' or 'Custom HTML' that contains user-supplied content
    Affected if Any form contains an HTML field with content that may include user input from form submissions
  4. Verify user role permissions for form editing
    Navigate to Formidable > Settings > Roles & Permissions, or check WordPress Users > Roles to see which roles have 'Form' edit capabilities
    Affected if Any user role below Administrator has permission to edit forms (Subscriber, Contributor, Author, or Editor)
  5. Inspect stored html field content for malicious scripts
    Edit each form containing an HTML field, view the field content in the form builder, and examine the database wp_postmeta table for postmeta_key containing 'frm_field_meta' or similar for the html field values
    Affected if The HTML field contains script tags, event handlers (onload, onerror, onclick), or suspicious URLs that were not intentionally added by an administrator

You are affected if Formidable Forms version is below 6.11.2 AND any user with Subscriber-level or higher access can edit forms containing HTML fields.

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

Update to version 6.11.2 or later which contains the fix for proper input sanitization and output escaping. Additionally, review and restrict form editing permissions to minimize the attack surface for lower-privileged users.

Recommended fix High confidence

Formidable Forms version 6.11.2

  1. Log in to the WordPress admin dashboard with administrator privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Formidable Forms' in the plugin list
  4. Check if the current version is below 6.11.2
  5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. Alternatively, navigate to Dashboard > Updates and select Formidable Forms to update
  7. After update, verify the plugin version shows 6.11.2 or higher
  8. Clear any caching plugins if active, then test form functionality to ensure the update did not break existing forms

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

Fix this in Formidable Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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