[FEATURE] Implement Payload all the things

### What's needed and why?

Everyone needs robust payload filtering to protect their website against common web attacks. However, configuring and maintaining such rules manually is time-consuming and mentally exhausting, especially as threat landscapes evolve.

### Implementations ideas (optional)

Add a built-in payload filtering mechanism that covers the most common attack payloads (SQLi, XSS, path traversal, etc.), drawing inspiration from the PayloadsAllTheThings repository as a reference for comprehensive coverage.
Reference: https://github.com/swisskyrepo/PayloadsAllTheThings

Discuss with @TheophileDiot

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start by reviewing the linked PayloadsAllTheThings repository and discuss scope with @TheophileDiot. Define which SQLi, XSS, and path-traversal payload classes are covered and how protection will be verified; the issue does not name files, entry points, or tests.

Written by the indexing model from the issue text.