High

Formie: Unauthenticated users can overwrite incomplete submissions via submit action

  • Disclosed: 23.09.2026
  • Updated: 11.10.2026 10:22

Impact

The anonymous front-end action formie/submissions/submit (SubmissionsController::actionSubmit) trusted a client-supplied submissionId when loading an incomplete submission, with no session binding, ownership check, or edit token validation.

An unauthenticated attacker could enumerate sequential submission IDs and overwrite or hijack another user's in-progress (multi-page / save-for-later) submission. Tampered data could be persisted and forwarded via notifications and integrations when the submission was completed.

Completed submissions were not affected (isIncomplete=true filter). This is an incomplete remediation of GHSA-pgxq-p76c-x9cg, which added edit-token validation to save-submission but not to submit.

Patches

Fixed in 3.1.31 (Craft 5) and 2.2.23 (Craft 4).

When resuming an existing submission on a site request, the submission ID must match the session-bound submission (Form::getCurrentSubmission()) or a valid submissionEditToken when editingSubmission is set. Cross-form submission ID reuse is also rejected.

Workarounds

No reliable workaround without upgrading. Disabling multi-page forms or save-for-later reduces exposure but does not remove the vulnerability.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package verbb/formie >= 3.0.0, < 3.1.31, < 2.2.23 3.1.31, 2.2.23

References

CVSS score 8.2/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Weakness (CWE)
CWE-639, CWE-862
Platform
Composer
Package
verbb/formie
Disclosed
23.09.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-584p-f93j-wpgc - CC BY 4.0

Vulnerability history: verbb/formie

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (10) in the archive
Total entries
10
First → latest
05.2024 09.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 4
  • Medium 4

Disclosures per year

  1. 2024: 1
  2. 2025: 2
  3. 2026: 7
Severity:
  1. High · 7.7 CVE-2026-76089 >= 3.0.0, < 3.1.31, < 2.2.23 3.1.31, 2.2.23
  2. Formie: Unauthenticated users can overwrite incomplete submissions via submit action this entry
    High · 8.2 CVE-2026-76087 >= 3.0.0, < 3.1.31, < 2.2.23 3.1.31, 2.2.23
  3. High · 8.5 CVE-2026-76086 >= 3.0.0, < 3.1.31, < 2.2.23 3.1.31, 2.2.23
  4. Critical · 9.8 CVE-2026-52889 < 3.1.27 3.1.27
  5. High CVE-2026-47266 >= 3.0.0, < 3.1.26, < 2.2.21 3.1.26, 2.2.21
  6. Critical · 9.8 CVE-2026-45697 >= 3.0.0-beta.1, < 3.1.24, < 2.2.20 3.1.24, 2.2.20

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.