Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-76087 – Unauthenticated Submission Hijacking – Formie Craft CMS Plugin (< 2.2.23, 3.0.0–3.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76087 is a missing authorization vulnerability in Formie, a form-building plugin for Craft CMS. The plugin’s anonymous formie/submissions/submit action fails to validate ownership of a submission ID before loading and updating it, allowing unauthenticated attackers to enumerate and overwrite other users’ incomplete, in-progress submissions. The issue carries a CVSS v3.1 base score of 8.2 (High).

Technical details

  • Root cause: The SubmissionsController::actionSubmit endpoint accepts a client-supplied submission ID and loads the corresponding incomplete submission without verifying that the requester owns it — there is no session binding, ownership check, or edit-token validation.
  • Trigger conditions: The submission must be incomplete (e.g., part of a multi-page or "save and continue later" form); completed submissions are unaffected and remain protected by existing filters.
  • Attack vector: A remote, unauthenticated attacker enumerates sequential or guessable submission IDs and submits requests to the anonymous endpoint to load and modify another user’s in-progress submission data.
  • Impact: Attackers can overwrite or hijack another user’s incomplete submission; the CVSS vector (C:L/I:H/A:N) reflects limited confidentiality impact but high integrity impact, since modified data can flow through to notifications and connected integrations.

Affected software

  • Formie (verbb/formie) for Craft CMS 4: versions prior to 2.2.23
  • Formie (verbb/formie) for Craft CMS 5: versions >= 3.0.0 and prior to 3.1.31

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Formie to version 2.2.23 (Craft CMS 4) or 3.1.31 (Craft CMS 5) or later, which enforce session-bound submission matching or valid edit-token verification when resuming a submission, and block cross-form reuse of submission IDs.
  • If no patch can be applied immediately: Restrict or monitor access to the formie/submissions/submit endpoint, review logs for anomalous sequential submission ID access patterns, and treat any multi-page or save-for-later form data as potentially tamperable until patched.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge