HTML Form Security

What is HTML Form Security?

Parses all <form> elements and checks for GET-method forms, password inputs without autocomplete="off", and the absence of CSRF token patterns (_token, csrf, _wpnonce, authenticity_token).

This vulnerability class falls under the Input Validation phase of the OWASP Testing Guide (WSTG-SESS). Security engineers prioritise input validation checks early in an assessment because weaknesses here provide a foothold that amplifies the severity of vulnerabilities found in later phases.

Security Impact

GET forms expose sensitive data in URLs, server logs, and Referer headers. Missing CSRF tokens allow cross-site request forgery. Password autocomplete risks credential leakage on shared devices.

Left undetected, html form security issues can persist unnoticed for months. Continuous automated scanning ensures your team receives an alert the moment a regression or new exposure is introduced — long before an attacker discovers it through manual enumeration or automated offensive tooling.

How DygDog Detects It

DygDog analyses session cookie attributes, transport security, and token entropy through passive observation of HTTP responses to map session-management weaknesses without interfering with live sessions.

The HTML Form Security check is implemented as a passive scan module, meaning it never sends dangerous payloads or modifies application state. Scans complete in approximately 400 ms and run continuously in the background so your security posture reflects the current state of your site — not a point-in-time snapshot.

Remediation Approach

Set the Secure, HttpOnly, and SameSite=Strict attributes on all session cookies; regenerate session identifiers after privilege elevation; and enforce absolute and idle session timeouts appropriate for your risk profile.

DygDog does not stop at detection. When a HTML Form Security finding is confirmed, the platform generates infrastructure-aware, copy-paste-ready remediation snippets using frontier AI models. Instead of generic advice you need to adapt, you receive code that targets your exact server, framework, and configuration.

OWASP References

This check maps to the following OWASP Testing Guide test cases:

• WSTG-SESS-05View OWASP WSTG →
• WSTG-INPV-01View OWASP WSTG →

Related Input Validation Checks

These checks belong to the same testing phase and are often assessed together:

• JavaScript Security Analysis

  Scans for outdated libraries (jQuery, Angular, Lodash), dangerous patterns (eval), and exposed source maps.

• DOM-Based XSS Analysis

  Identifies DOM XSS sources (location, document.URL) and sinks (innerHTML, eval) in JavaScript code.

• Clickjacking Protection

  Verifies X-Frame-Options and CSP frame-ancestors protection against UI redressing attacks.

• WebSocket Security

  Detects WebSocket connections, checks for wss:// enforcement, and analyses handshake security.