Skip to content
faker.tools
All 79

Plate VIII · Localization, Edge Cases & Data Sanitizers

Security Test Payload Generator

Canonical injection strings for validating your own input handling.

#PayloadNameFamilyExpected Behaviour
1' OR '1'='1Classic tautologysqliStored and returned verbatim; the query uses bound parameters.
2admin'--Comment terminatorsqliStored and returned verbatim; the query uses bound parameters.
3' UNION SELECT NULL,NULL--Union probesqliStored and returned verbatim; the query uses bound parameters.
41; DROP TABLE users--Stacked querysqliStored and returned verbatim; the query uses bound parameters.
5' AND 1=1--Boolean blindsqliStored and returned verbatim; the query uses bound parameters.
61 OR 1=1Numeric bypasssqliStored and returned verbatim; the query uses bound parameters.
7<script>alert(1)</script>Script tagxssRendered as visible text, never as markup.
8<img src=x onerror=alert(1)>Image onerrorxssRendered as visible text, never as markup.
9<svg onload=alert(1)>SVG onloadxssRendered as visible text, never as markup.
10" autofocus onfocus=alert(1) x="Attribute break-outxssRendered as visible text, never as markup.
10 rows · 1.7 KBGenerated in your browser · Security Test Payload Generator

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.

Questions

What is this for?

Confirming that your own input handling is safe. You paste a payload into your form and verify it comes back as visible text, not as executed markup or a modified query.

Why does the encoding matter?

Because filters are often applied at one layer and bypassed at another. A payload blocked in raw form may pass URL-encoded and get decoded later, which is where the vulnerability lives.

Are these actual exploits?

No. They are the canonical detection strings published in every security testing guide. They reveal whether a vulnerability exists; they do not exploit one.

Next in Edge cases

All 7 →