HT Contact Form
BitFire's WAF detects and blocks the unauthenticated stored DOM-based XSS payload in HT Contact Form ≤ 2.10.1 before WordPress processes the request.
- Affected sites
- 10,000+
- Attack class
- Stored Dom-based Cross-site Scripting
Review the attack behind each advisory and the BitFire control—bot protection, WAF, or runtime RASP—that prevents it from becoming a compromise.
Showing 25–30 of 52 records · Updated October 9, 2026
BitFire's WAF detects and blocks the unauthenticated stored DOM-based XSS payload in HT Contact Form ≤ 2.10.1 before WordPress processes the request.
BitFire FREE blocks the double-encoded traversal local file inclusion before vulnerable WordPress template resolution can include an attacker-selected PHP file.
BitFire FREE detects the serialized PHP object behind CVE-2026-82222 before GiveWP can deserialize it and trigger remote code execution.
BitFire blocks malicious uploads and PRO RASP prevents unauthorized PHAR creation through the vulnerable Contact Form 7 add-on.
BitFire PRO RASP blocks unauthorized PHP-file writes that turn the Avada and Fusion Builder flaw into persistent server compromise.
ManageWP Worker authentication bypass can log attackers in as other users, while BitFire PRO RASP blocks unauthorized session creation.
Page 5 of 9
BitFire combines bot controls, request inspection, and runtime enforcement so emerging vulnerabilities fail before a CVE-specific rule exists.