CVE-2026-76087: Formie: Unauthenticated users can overwrite incomplete submissions via submit action
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.
Published Sep 23, 2026
Affected packages
verbb/formie
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0, < 3.1.31
- Fixed in
- 3.1.31
- Check
composer show verbb/formie
verbb/formie
- Ecosystem
- Composer (PHP)
- Affected
- < 2.2.23
- Fixed in
- 2.2.23
- Check
composer show verbb/formie
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
- Reported by Jorge González ([email protected])
Credited to Pig-Tail.
References
- https://github.com/verbb/formie/security/advisories/GHSA-584p-f93j-wpgc
- https://github.com/verbb/formie/commit/323c2fe647a76fbccadf749728ee4ad9420efee1
- https://github.com/verbb/formie/commit/78a298ac3baf85ac283988dfce9cd42c9b958f16
- https://github.com/verbb/formie/releases/tag/2.2.23
- https://github.com/verbb/formie/releases/tag/3.1.31
- https://github.com/advisories/GHSA-584p-f93j-wpgc
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-76086
Formie: Integration form-settings action allows SSRF and exfiltration of stored integration credentials
high8.5Sep 23, 2026CVE-2026-76089
Formie: Missing authorization on sent notification resend modal exposes submission PII
high7.7Sep 23, 2026GHSA-cvpc-hccg-wmw4
Formie: Missing authorization in administrative settings allows low-privileged CP users to modify plugin configuration
medium6.3Jul 17, 2026CVE-2026-52889
Formie Hidden field defaults vulnerable to Server-Side Template Injection
critical9.8Jul 6, 2026CVE-2026-47266
formie's unauthenticated front-end submission editing can overwrite existing submissions
high8.7May 29, 2026CVE-2026-45697
Formie: Pre-authenticated server-side template injection in Hidden fields
critical9.8May 18, 2026
