What we look for
These pages hold a form whose action (the address it sends what visitors type to) starts with http://, so the data travels unencrypted.
Why it matters
Anyone on the same network can read what visitors submit, such as names, emails or passwords, and browsers warn people before sending it.
How to fix
Change each form's action address to https:// in the page template or form plugin settings, and make sure the address it points to accepts secure requests.
Where you’ll see it
The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.
- Terminal
- When it is one of the five findings under Fix first,
raptor crawlprints the id under it.Check: security.
insecure_ form_ action - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "security. insecure_ form_ action" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= security. insecure_ form_ action - MCP
raptor_findingswith thischeck_idreturns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.raptor_
findings { "job_ id": ". . . ", "check_ id": "security. insecure_ form_ action" }