These are the published, widely documented test strings that appear in every security checklist — ' OR '1'='1, <script>alert(1)</script>, ../../etc/passwd. Their job here is to be pasted into your own form so you can confirm nothing happens.
What you can control
- Nine payload families covering the injection classes that appear in the OWASP Top Ten.
- Each payload comes with the behaviour a correctly written handler should show, so you know what you are checking for.
- Four encodings, because a payload that is blocked raw often gets through URL-encoded.
- These are canonical, published strings — no novel exploits, no evasion techniques.
Testing ideas
- Expected behaviour. Use the "what a safe handler should do" column as the assertion: stored and echoed verbatim, never executed.
- Encodings. Generate URL-encoded, HTML-escaped and JSON-string variants to test each layer of decoding.
- Regression suites. Export the payloads into a parameterised test that runs on every build.
- Only where authorised. Test applications you own or have written permission to test. These payloads are for defence, not for probing other people's systems.
What this is not
Use these against systems you own or have written permission to test. Running them against someone else's application without authorisation is illegal in most jurisdictions, regardless of intent.