Formie: Integration form-settings action allows SSRF and exfiltration of stored integration credentials
Published 23 Sept 2026 · Updated 24 Sept 2026
Is your project on an affected verbb/formie?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=3.0.0 <3.1.31
- Fixed in
- 3.1.31
composer require verbb/formie:^3.1.31- Affected
- <2.2.23
- Fixed in
- 2.2.23
composer require verbb/formie:^2.2.23Details
Impact
The control panel action formie/integrations/form-settings (IntegrationsController::actionFormSettings) was reachable by any authenticated user without the appropriate form integration permissions. The action applied request-supplied settings to a fully configured integration via setAttributes($settings, false), allowing an attacker to overwrite outbound host properties (e.g. apiUrl) while the server sent stored API keys or OAuth tokens to the attacker-controlled host. The remote response was returned in the JSON body (non-blind SSRF).
This is an incomplete remediation of GHSA-cvpc-hccg-wmw4. The form-settings action was excluded from the permission gate added in 3.1.28.
Any site where a low-privileged user can authenticate (including front-end members on sites with public registration) could exfiltrate CRM/email-marketing/webhook integration credentials and probe internal network endpoints.
Patches
Fixed in 3.1.31 (Craft 5) and 2.2.23 (Craft 4).
The action now requires a CP request, a valid formId, and form integration permissions (formie-showFormIntegrations / per-form variant on Craft 5; formie-manageFormIntegrations / per-form variant on Craft 4). Request settings are filtered to an allowlist; URL, host, and credential properties cannot be overridden from user input.
Workarounds
Restrict front-end user registration and limit CP access until upgraded. No configuration-only workaround fully mitigates the issue.
- Reported by Jorge González (jorge@jmilla.es)
Is GHSA-v3f3-cmj4-cvj9 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected verbb/formie, and gives you the command that fixes it.
More advisories for verbb/formie
- HighCVE-2026-76089Formie: Missing authorization on sent notification resend modal exposes submission PII · 23 Sept 2026
- HighCVE-2026-76087Formie: Unauthenticated users can overwrite incomplete submissions via submit action · 23 Sept 2026
- MediumGHSA-cvpc-hccg-wmw4Formie: Missing authorization in administrative settings allows low-privileged CP users to modify plugin configuration · 17 Jul 2026
- CriticalCVE-2026-52889Formie Hidden field defaults vulnerable to Server-Side Template Injection · 6 Jul 2026
- HighCVE-2026-47266formie's unauthenticated front-end submission editing can overwrite existing submissions · 29 May 2026
- CriticalCVE-2026-45697Formie: Pre-authenticated server-side template injection in Hidden fields · 18 May 2026
References
- Linkgithub.com/verbb/formie/security/advisories/GHSA-v3f3-cmj4-cvj9
- Linkgithub.com/verbb/formie/commit/6735fe4ae8f6a2a76930716ad7876b236f7c530d
- Linkgithub.com/verbb/formie/commit/dde7799dfa7e4d0a11e28754ad8544dba62d5def
- Advisorygithub.com/advisories/GHSA-cvpc-hccg-wmw4
- Packagegithub.com/verbb/formie
- Linkgithub.com/verbb/formie/releases/tag/2.2.23
- Linkgithub.com/verbb/formie/releases/tag/3.1.31
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.