top-web-vulnerabilities
Skill0 starsChanged 10 months agoMITView on GitHub
Comprehensive reference for the OWASP Top 100 web vulnerabilities. Identifies vulnerable patterns, explains impacts, and provides remediation guidance across injection attacks, authentication flaws, data exposure, and advanced attack vectors.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- zebbern/claude-code-guidetheir own version, first seen Oct 30, 2026
- Ghosteken/agent-harnesstheir own version, first seen Oct 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- zebbern/claude-code-guide★ 4.7ksame name
- Ghosteken/agent-harness★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- architectSkill
- brainstormingSkill
- concise-planningSkill
- context-engineerSkill
- data-deprecation-analysisSkill
- data-modelerSkill
- data-pipeline-engineerSkill
- data-quality-frameworksSkill
- dbt-transformation-patternsSkill
- github-workflow-automationSkill
- guardianSkill
- implementerSkill
- json-to-pydanticSkill
- llm-app-patternsSkill
- navigatorSkill
- ops-managerSkill
- orchestratorSkill
- principal-data-engineerSkill
- product-manager-toolkitSkill
- proj-memorySkill
- prompt-librarySkill
- qa-testerSkill
- researcherSkill
- senior-data-engineerSkill
- software-architectureSkill
- spark-optimizationSkill
- sql-optimization-patternsSkill
- state-managerSkill
- subagent-driven-developmentSkill
- thinkerSkill
- verification-before-completionSkill
- web-design-guidelinesSkill
- workflow-managerSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 128
Check for injection vulnerabilities (SQL, XSS, command)
- Distinctive: line 129
Verify authorization checks on sensitive operations
- Distinctive: line 134
Check security headers (CSP, HSTS, X-Frame-Options)
- Distinctive: line 135
Verify HTTPS/TLS configuration
- Distinctive: line 138
Check for default credentials and debug features
- Distinctive: line 142
Test authentication (brute force, session fixation)
- Distinctive: line 143
Test authorization (IDOR, privilege escalation)
- Distinctive: line 144
Test input validation (injection, XSS)
- Distinctive: line 145
Test rate limiting and DoS protections
- Distinctive: line 146
Test data encryption and HTTPS
- Distinctive: line 151
Add unit/integration tests for vulnerabilities
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Top 100 Web Vulnerabilities
Comprehensive reference for the OWASP Top 100 most critical web application vulnerabilities.
When to Use This Skill
Use when:
- Identifying web application vulnerabilities during code review
- Explaining common security flaws to developers
- Understanding vulnerability categories and impacts
- Providing remediation guidance for security findings
- Testing for OWASP-listed vulnerabilities
- Building secure applications and avoiding known patterns
- Assessing application security posture
- Training on secure coding practices
Core Capabilities
- Injection & Input Validation - SQL, XSS, command, template injection attacks
- Authentication & Authorization - Session management, privilege escalation, IDOR
- Data Exposure & Configuration - Information disclosure, misconfiguration, missing headers
- Advanced Attacks - Deserialization, SSRF, DoS, race conditions
- API & Transport Security - Insecure APIs, MITM, TLS configuration
- Client-Side Security - DOM-based XSS, clickjacking, browser cache poisoning
- Business Logic Flaws - Workflow abuse, payment bypass, authorization logic
Vulnerability References
For detailed vulnerability guidance, see:
Injection & Input Validation Vulnerabilities
Use when: Identifying and fixing injection attacks
Covers:
- SQL Injection (OWASP #1)
- Cross-Site Scripting - XSS (OWASP #2)
- Command Injection (OWASP #5, #11)
- XML Injection variants (XXE, XPath, LDAP, SSTI)
- Server-Side Template Injection (OWASP #13)
Authentication & Authorization Flaws
Use when: Securing authentication and access control
Covers:
- Session Fixation (OWASP #14)
- Brute Force Attacks (OWASP #15)
- Session Hijacking (OWASP #16)
- Credential Stuffing (OWASP #22)
- IDOR - Insecure Direct Object References (OWASP #23, #42)
- Privilege Escalation (OWASP #41)
- Forceful Browsing (OWASP #43)
Data Exposure & Configuration Flaws
Use when: Protecting sensitive data and securing configuration
Covers:
- Data Leakage (OWASP #24)
- Unencrypted Data Storage (OWASP #25)
- Missing Security Headers (OWASP #26)
- Default Passwords (OWASP #28)
- Information Disclosure (OWASP #33)
- Unprotected APIs (OWASP #30)
- Misconfigured CORS (OWASP #35)
Advanced Attack Vectors
Use when: Addressing complex attack scenarios
Covers:
- Insecure Deserialization (OWASP #45-47)
- Server-Side Request Forgery - SSRF (OWASP #66)
- Distributed Denial of Service (OWASP #61, #62)
- Resource Exhaustion (OWASP #63)
- Request timeouts and rate limiting
Quick Vulnerability Lookup
| Category | OWASP # | Vulnerability | Reference |
| Injection | 1 | SQL Injection | Injection Vulnerabilities |
| Injection | 2 | Cross-Site Scripting (XSS) | Injection Vulnerabilities |
| Auth | 14 | Session Fixation | Auth & Authorization |
| Auth | 15 | Brute Force | Auth & Authorization |
| Auth | 16 | Session Hijacking | Auth & Authorization |
| Auth | 23 | IDOR | Auth & Authorization |
| Data | 24 | Data Leakage | Data Exposure |
| Data | 25 | Unencrypted Storage | Data Exposure |
| Data | 33 | Information Disclosure | Data Exposure |
| Advanced | 45 | Insecure Deserialization | Advanced Attacks |
| Advanced | 66 | SSRF | Advanced Attacks |
Assessment Workflow
Phase 1: Code Review
- Identify user input entry points (forms, APIs, cookies)
- Trace input through application (filters, validation, storage)
- Check for injection vulnerabilities (SQL, XSS, command)
- Verify authorization checks on sensitive operations
- Review encryption and data protection
Phase 2: Configuration Review
- Check security headers (CSP, HSTS, X-Frame-Options)
- Verify HTTPS/TLS configuration
- Review API authentication and rate limiting
- Audit access controls and IAM
- Check for default credentials and debug features
Phase 3: Testing
- Test authentication (brute force, session fixation)
- Test authorization (IDOR, privilege escalation)
- Test input validation (injection, XSS)
- Test rate limiting and DoS protections
- Test data encryption and HTTPS
Phase 4: Remediation
- Implement fixes with highest severity first
- Add unit/integration tests for vulnerabilities
- Perform regression testing
- Deploy with monitoring
- Document security improvements
Best Practices
Input & Output Handling
- ✅ Validate Input: Whitelist acceptable input patterns
- ✅ Encode Output: Escape data based on context (HTML, JavaScript, SQL)
- ✅ Parameterized Queries: Use prepared statements for databases
- ✅ Content Security Policy: Implement CSP headers
Authentication & Authorization
- ✅ Strong Passwords: Enforce complexity, minimum length
- ✅ MFA: Implement multi-factor authentication
- ✅ Rate Limiting: Limit failed login attempts
- ✅ Least Privilege: Grant minimum necessary permissions
- ✅ Session Security: HttpOnly, Secure, SameSite cookie flags
Data Protection
- ✅ Encryption in Transit: Use TLS 1.2+ with strong ciphers
- ✅ Encryption at Rest: Encrypt PII and sensitive data
- ✅ Secrets Management: Use vaults, never hardcode secrets
- ✅ Data Minimization: Only collect and store necessary data
- ✅ Access Logging: Audit and alert on sensitive data access
Security Configuration
- ✅ Security Headers: CSP, HSTS, X-Frame-Options, X-Content-Type-Options
- ✅ Disable Debug Mode: No stack traces or error details in production
- ✅ Change Defaults: Remove default credentials and configurations
- ✅ Patch Management: Keep frameworks, libraries, and OS updated
- ✅ Security Scanning: Regular SAST/DAST scans
Dependencies
- guardian - For security review and compliance verification
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.