vulns.co
/
GKData.io MCP and API Buy me a coffee

Verbb / Formie

Formie: integration settings need operation and attribute authority

Formie's maintainer reports that weak permission checks and overly broad settings changes could expose stored integration credentials. Callers could change the destination used with those credentials, and the advisory also describes server-side requests whose responses were returned to the caller. The lesson is to restrict both who can change integration settings and which sensitive fields they can change.

Open the referenceMaintainer AdvisoryReviewed 2026-10-04

How to use this reference

The two branch-specific patches require control-panel request context, a valid form and integration permission, then limit mutable settings while excluding destination and credential properties. Editorial lesson: operation authorization and attribute authority are complementary controls; possessing an authenticated session does not establish either. Review alternate entry points after a shared permission repair. The official releases identify 2.2.23 for Craft 4 and 3.1.31 for Craft 5 as patched.

Before reading

  • Distinguishing authentication from operation-specific authorization
  • Understanding settings mutation and credential-bearing integration requests

Context and limits

  • The described case requires an affected installation and an authenticated caller, including a front-end member; credential impact additionally depends on a configured integration holding credentials.
  • The advisory identifies incomplete earlier authorization remediation. Temporary restrictions on registration and control-panel access are not a complete configuration-only fix.
  • The reviewed sources provide no controlled test transcript, production incident, victim count or independent reproduction. Downstream account takeover or cloud compromise is not established. No individual award is established.
  • The advisory body credits Jorge González as reporter; its formal credit lists Pig-Tail as Finder. Their identity relationship is not established here. engram-design is the publishing account, not an explicit narrative byline, so authors remains empty.
  • The GitHub database records its own publication and review on September 23, 2026. The official release APIs give July 9, 2026 at 12:21:35 UTC for 2.2.23 and 12:26:02 UTC for 3.1.31. Software release, advisory publication, database entry, educational edition and installation-specific deployment are separate events; deployment dates remain unknown.

Sources

  1. Formie integration-settings security advisoryVerbb / Formie · reviewed 2026-10-04
  2. GitHub Advisory Database entry for CVE-2026-76086GitHub · reviewed 2026-10-04
  3. Formie Craft 4 integration authorization and settings restriction patchVerbb / Formie · reviewed 2026-10-04
  4. Formie Craft 5 integration authorization and settings restriction patchVerbb / Formie · reviewed 2026-10-04
  5. Official Formie 2.2.23 release metadataVerbb / Formie · reviewed 2026-10-04
  6. Official Formie 3.1.31 release metadataVerbb / Formie · reviewed 2026-10-04

Record reviewed 2026-10-04. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software