Cross-Site Scripting (XSS) in Contact Form to Email (CVE-2021-47926)
Summary
Cross-site scripting in Contact Form to Email (CVE-2021-47926). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Contact Form to Email 1.3.24 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts by creating forms with script tags in the form name field. Attackers can craft form names containing JavaScript code that executes when other logged-in users access the form management page, enabling session hijacking or credential theft.
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-2021-47926 has been found in Contact Form to Email.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Contact Form to Email CVE-2021-47926" on the vendor's site.
CVE-2021-47926 (Contact Form to Email) — CWE-79 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
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.
Cross-site scripting (XSS) (CWE-79) exists in Contact Form to Email.
Check the vendor advisory for the affected versions of Contact Form to Email.
Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Contact Form to Email を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。