Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

Formie: Unauthenticated users can overwrite incomplete submissions via submit action

CVE-2026-76087GHSA-584p-f93j-wpgc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (verbb/formie 3.1.31, 2.2.23), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist verbb/formie

    Affected
    >= 3.0.0, < 3.1.31< 2.2.23
    Fixed in
    2.2.23, 3.1.31

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
EPSS
  • CVE-2026-76087: 0.41% estimated exploitation activity in the next 30 days; percentile 35.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-584p-f93j-wpgc

  2. Revision 1 · created ·

    Published from osv record GHSA-584p-f93j-wpgc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-76087

Advisory: Formie: Unauthenticated users can overwrite incomplete submissions via submit action
IDs: CVE-2026-76087, GHSA-584p-f93j-wpgc
Record: https://patchnext.com/advisories/cve-2026-76087 (revision 2, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: verbb/formie 3.1.31, 2.2.23. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist verbb/formie: affected >= 3.0.0, < 3.1.31; < 2.2.23; fixed in 2.2.23, 3.1.31

## Suggested inspection (read-only)
- Packagist verbb/formie: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on verbb/formie.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-584p-f93j-wpgc (OSV record GHSA-584p-f93j-wpgc lists affected ranges: Packagist verbb/formie >=3.0.0 =0 <2.2.23 (fixed))
- Verified: https://github.com/advisories/GHSA-584p-f93j-wpgc (GitHub-reviewed advisory GHSA-584p-f93j-wpgc lists affected ranges: Packagist verbb/formie >=3.0.0 =0 <2.2.23)

Commands are suggestions: review each one before running it.

Loading voting…