Vulnerability in verbb/formie (CVE-2026-47266)
Summary
Vulnerability in verbb/formie (CVE-2026-47266). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.2.21 or later.
Original description
The description as published by the source.
Formie is a Craft CMS plugin for creating forms. Prior to 2.2.21 and 3.1.26, unauthenticated users could modify existing submissions by posting a known or guessed submission ID to formie/submissions/save-submission. This vulnerability is fixed in 2.2.21 and 3.1.26.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47266 has been found in verbb/formie.
Risk of unauthorized operations or information disclosure.
What to do: upgrade verbb/formie to 2.2.21 or later.
If unsure, ask your IT team or search "verbb/formie CVE-2026-47266" on the vendor's site.
CVE-2026-47266 (verbb/formie) — CWE-639
Patched: 2.2.21 — apply immediately
Workaround: Block unauthenticated access to actions/formie/submissions/save-submission, or disable/customize front-end submission editing until patched.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in verbb/formie.
Check the vendor advisory for the affected versions of verbb/formie.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.2.21.
Workaround: Block unauthenticated access to actions/formie/submissions/save-submission, or disable/customize front-end submission editing until patched.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'verbb/formie' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'verbb/formie' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
verbb/formieを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Block unauthenticated access to `actions/formie/submissions/save-submission`, or disable/customize front-end submission editing until patched.パッチが適用されるまでの応急処置として、Block unauthenticated access to
actions/formie/submissions/save-submission, or disable/customize front-end submission editing until patched. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade verbb/formie to 2.2.21ステージング環境で 2.2.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com