dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-47266

HIGH · 8.7 CVSS v4.0 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
Formie is a Craft CMS plugin for creating forms. Prior to 2.2.21 and 3.1.26, unauthenticated users could modify existing submissions by posting a known or guessed submission ID to formie/submissions/save-submission. This vulnerability is fixed in 2.2.21 and 3.1.26.

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

IDOR vulnerability in Formie plugin for Craft CMS allows unauthenticated attackers to modify existing form submissions by sending POST requests with known or guessed submission IDs to the formie/submissions/save-submission endpoint, enabling unauthorized data tampering.

MitigationUpgrade Formie plugin to version 2.2.21 or 3.1.26 or later to patch the insecure direct object reference vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Formie plugin is installed
    In Craft CMS admin, go to Settings > Plugins, or check the /craft/plugins/ directory for the Formie plugin folder
    Affected if Formie plugin is not present in the Craft CMS installation
  2. Determine installed Formie version
    In Craft CMS admin, go to Settings > Plugins and note the version number displayed next to Formie. Alternatively, check the composer.json file in the Formie plugin directory for the 'version' field
    Affected if Version is below 2.2.21 for Craft CMS v2 installations, or below 3.1.26 for Craft CMS v3 installations
  3. Verify submission save endpoint is accessible
    Check if the endpoint /actions/formie/submissions/save-submission is reachable without authentication. This can be confirmed by examining the Craft CMS routing configuration or by attempting a POST request to this endpoint with a test submission ID while unauthenticated
    Affected if The endpoint accepts requests without requiring a logged-in user session
  4. Check for existing submissions with predictable IDs
    Review form submission logs or database tables (typically with a 'formie_submissions' prefix) to confirm whether submission IDs are sequential or predictable integers
    Affected if Submission IDs are sequential (e.g., 1, 2, 3...) making them guessable by unauthenticated users

A user is affected if Formie plugin is installed with version below 2.2.21 (v2) or below 3.1.26 (v3) AND the submission save endpoint is accessible to unauthenticated users, allowing modification of any submission if the ID is known or guessable.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Formie plugin to version 2.2.21 or 3.1.26 or later to patch the insecure direct object reference vulnerability.

Recommended fix High confidence

Formie plugin version 2.2.21 (for Craft CMS 2.x) or 3.1.26 (for Craft CMS 3.x)

  1. Identify the currently installed version of the Formie plugin in your Craft CMS installation
  2. Determine which major version of Craft CMS (2.x or 3.x) is running, as Formie has separate release tracks for each
  3. Backup your database and files before performing any updates
  4. Update the Formie plugin to version 2.2.21 (for Craft 2.x) or version 3.1.26 (for Craft 3.x) via the Craft CMS control panel plugin store, or via Composer if using command-line management
  5. Verify the plugin updated successfully by checking the installed version in the control panel
  6. Test that the /formie/submissions/save-submission endpoint properly enforces authorization and rejects unauthorized modification attempts

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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