dbcve.org
Formidable FormsWordPress extension · Strategy11

CVE-2022-45806

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 5.5.5 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 Strategy11 Form Builder Team Formidable Forms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Formidable Forms: from n/a through 5.5.4.

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 Formidable Forms WordPress plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to sensitive functionality or data without proper authentication or privilege validation.

MitigationUpdate Formidable Forms to the latest patched version immediately. Review and enforce proper role-based access control (RBAC) checks on all sensitive endpoints and functionality.

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:< 5.5.5

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. Check Formidable Forms plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Formidable Forms and read the version number. Alternatively, inspect /wp-content/plugins/formidable/formidable.php and look for the 'Version:' comment header.
    Affected if The installed version is lower than 5.5.5 (e.g., 5.5.4, 5.5.3, etc.)
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify Formidable Forms shows as 'Active' under the plugin status.
    Affected if The plugin is installed and active, and the version is below 5.5.5
  3. Verify WordPress REST API accessibility
    Test unauthenticated access to WordPress REST API endpoints related to Formidable Forms by sending a GET request to /wp-json/formidable/ or similar routes without providing authentication credentials.
    Affected if REST API endpoints for Formidable Forms respond without requiring authentication and the plugin version is below 5.5.5
  4. Inspect user role capabilities
    Review WordPress user roles and capabilities at Users > Roles, or use a role management plugin to check if low-privilege users (subscriber, contributor) can access Formidable Forms administrative features or entries.
    Affected if Users with subscriber-level access can view or modify Formidable Forms data without proper authorization checks, and the plugin version is below 5.5.5

You are affected if Formidable Forms plugin is active with a version lower than 5.5.5 and sensitive functionality is accessible without proper authentication or authorization validation.

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

Update Formidable Forms to the latest patched version immediately. Review and enforce proper role-based access control (RBAC) checks on all sensitive endpoints and functionality.

Recommended fix High confidence

Formidable Forms version 5.5.5 or later

  1. 1. Create a full backup of your WordPress site including database and files
  2. 2. Navigate to Plugins > All Plugins in your WordPress admin dashboard
  3. 3. Find Formidable Forms in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually upload version 5.5.5 or later from the WordPress repository
  5. 5. Verify the update was successful by checking the plugin version in the Plugins list
  6. 6. Test that forms still function correctly and authorization controls are working as expected

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
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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