dbcve.org
Formidable FormsWordPress extension · Strategy11

CVE-2024-23522

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 6.7.1 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Strategy11 Form Builder Team Formidable Forms allows Code Injection.This issue affects Formidable Forms: from n/a through 6.7.

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 stored Cross-Site Scripting (XSS) vulnerability in the Formidable Forms WordPress plugin. The plugin fails to properly sanitize or escape user-supplied input in forms, allowing attackers to inject malicious HTML/script tags that execute in the browsers of users viewing form data.

MitigationUpdate Formidable Forms to the latest patched version. If immediate update is not possible, implement output encoding and input validation on all form fields displaying user content, or disable public form submissions until the patch is applied.

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.7.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Formidable Forms plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find Formidable Forms, or run: wp plugin list --name=formidable --format=json, or inspect /wp-content/plugins/formidable/formidable.php and look for the Version header comment
    Affected if The installed version is lower than 6.7.1 (e.g., 6.7.0, 6.6.x, etc.)
  2. Confirm public form submissions are enabled
    In WordPress admin, go to Formidable > Forms and check if any forms have the status set to 'Published' and are configured to allow public (non-logged-in) submissions under form settings
    Affected if Public-facing forms exist and accept submissions from unauthenticated users, allowing malicious input to be stored
  3. Identify forms that display submitted user data
    In WordPress admin, review forms that include fields likely to capture user input (text fields, textareas, dropdowns) and check if Form Views or Entries are configured to display this data to users
    Affected if Forms store and display user-submitted content to other users or administrators without additional sanitization layers in place

You are affected if Formidable Forms version is below 6.7.1 AND you have published forms that accept and display user-submitted content.

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.7.1 or later
Fixed in 6.7.1
Interim mitigation

Update Formidable Forms to the latest patched version. If immediate update is not possible, implement output encoding and input validation on all form fields displaying user content, or disable public form submissions until the patch is applied.

Recommended fix Moderate confidence

6.7.1

  1. 1. Back up your WordPress site and database before making any updates
  2. 2. Navigate to the WordPress admin dashboard > Plugins
  3. 3. Find Formidable Forms in the plugins list and click 'Update Now'
  4. 4. Alternatively, go to Plugins > Add New > Upload and upload version 6.7.1 or later of the Formidable Forms plugin
  5. 5. After updating, verify the plugin version shows 6.7.1 or higher in the Plugins list
  6. 6. Test critical 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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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