SecLists icon indicating copy to clipboard operation
SecLists copied to clipboard

SecLists is the security tester's companion. It's a collection of multiple types of lists used during security assessments, collected in one place. List types include usernames, passwords, URLs, sensi...

Results 187 SecLists issues
Sort by recently updated
recently updated
newest added

https://github.com/danielmiessler/SecLists/blame/dc7f0f98a936e71dc083378ba8a2655132e25d65/Discovery/Web-Content/common.txt#L1427C7-L1427C7 I did not install any of this on my phone and I want to remove it I cannot figure out how please and thank you you are messing with...

check keycloak for sensitive paths.

These prompts are crafted to challenge the models in various ways, including but not limited to their ability to follow ethical guidelines, maintain data privacy, resist generating harmful or sensitive...

Hi, This PR add the endpoint exposed when the target supports DNS over HTTP requests. 📖My sources were the following ones: * https://developers.cloudflare.com/1.1.1.1/encryption/dns-over-https/make-api-requests/ * https://github.com/projectdiscovery/nuclei-templates/blob/main/http/miscellaneous/detect-dns-over-https.yaml 👀If the target supports DNS...

This pull request fixes the following bugs 🐛 in the Seclists Github Actions: - Some wordlists were executing on every single commit instead of only executing when one of the...

Hey Daniel, Not sure if this is the right section, i was doubting if it needed to be in wordlist added or just a question, i noticed that in the...

question

I've added `.phar` to `extensions-most-common.fuzz.txt`..

**Describe the bug**: **To reproduce**: **Expected behaviour**: **Screenshots**: **Additional context**: **Next steps**: - [x] I intend to open a pull request later

bug

**Feature Request**: Create a wordlist for safe SQL Injection fuzzing that doesn't contain dangerous parameters **Additional context**: Logical operators like `' OR 1=1` can be dangerous if successfully injected on...

help wanted

**Describe the bug**: **To reproduce**: **Expected behaviour**: **Screenshots**: **Additional context**: **Next steps**: - [x] I intend to open a pull request later

bug