TO

top-100-web-vulnerabilities-reference

This reference provides a catalog of 100 web vulnerabilities, detailing their root causes, impact, and remediation steps.

Install

mkdir -p .claude/skills/top-100-web-vulnerabilities-reference && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/799" && unzip -o skill.zip -d .claude/skills/top-100-web-vulnerabilities-reference && rm skill.zip

Installs to .claude/skills/top-100-web-vulnerabilities-reference

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

This skill should be used when the user asks to "identify web application vulnerabilities", "explain common security flaws", "understand vulnerability categories", "learn about injection attacks", "review access control weaknesses", "analyze API security issues", "assess security misconfigurations", "understand client-side vulnerabilities", "examine mobile and IoT security flaws", or "reference the OWASP-aligned vulnerability taxonomy". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.
597 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Map specific security threats to 15 standardized vulnerability categories
  • Perform systematic injection vulnerability assessments
  • Identify common misconfigurations in API and web architecture
  • Generate structured remediation strategies based on identified root causes
  • Categorize flaws by attack vector type

How it works

Applies an industry-standard taxonomy to the provided codebase or system description to isolate flaws and suggest corrective patterns.

Inputs & outputs

You give it
Target application architecture description or code snippet
You get back
Categorized vulnerability report with impact analysis and mitigation steps

When to use top-100-web-vulnerabilities-reference

  • Review code for common injection vulnerabilities
  • Assess security flaws in an API implementation
  • Learn about access control best practices

About this skill

Top 100 Web Vulnerabilities Reference

Purpose

Provide a comprehensive, structured reference for the 100 most critical web application vulnerabilities organized by category. This skill enables systematic vulnerability identification, impact assessment, and remediation guidance across the full spectrum of web security threats. Content organized into 15 major vulnerability categories aligned with industry standards and real-world attack patterns.

Prerequisites

  • Basic understanding of web application architecture (client-server model, HTTP protocol)
  • Familiarity with common web technologies (HTML, JavaScript, SQL, XML, APIs)
  • Understanding of authentication and authorization concepts
  • Access to web application security testing tools (Burp Suite, OWASP ZAP)
  • Knowledge of secure coding principles recommended

Outputs and Deliverables

  • Complete vulnerability catalog with definitions, root causes, impacts, and mitigations
  • Category-based vulnerability groupings for systematic assessment
  • Quick reference for security testing and remediation
  • Foundation for vulnerability assessment checklists and security policies

Core Workflow

Phase 1: Injection Vulnerabilities Assessment

Evaluate injection attack vectors targeting data processing components:

SQL Injection (1)

  • Definition: Malicious SQL code inserted into input fields to manipulate database queries
  • Root Cause: Lack of input validation, improper use of parameterized queries
  • Impact: Unauthorized data access, data manipulation, database compromise
  • Mitigation: Use parameterized queries/prepared statements, input validation, least privilege database accounts

Cross-Site Scripting - XSS (2)

  • Definition: Injection of malicious scripts into web pages viewed by other users
  • Root Cause: Insufficient output encoding, lack of input sanitization
  • Impact: Session hijacking, credential theft, website defacement
  • Mitigation: Output encoding, Content Security Policy (CSP), input sanitization

Command Injection (5, 11)

  • Definition: Execution of arbitrary system commands through vulnerable applications
  • Root Cause: Unsanitized user input passed to system shells
  • Impact: Full system compromise, data exfiltration, lateral movement
  • Mitigation: Avoid shell execution, whitelist valid commands, strict input validation

XML Injection (6), LDAP Injection (7), XPath Injection (8)

  • Definition: Manipulation of XML/LDAP/XPath queries through malicious input
  • Root Cause: Improper input handling in query construction
  • Impact: Data exposure, authentication bypass, information disclosure
  • Mitigation: Input validation, parameterized queries, escape special characters

Server-Side Template Injection - SSTI (13)

  • Definition: Injection of malicious code into template engines
  • Root Cause: User input embedded directly in template expressions
  • Impact: Remote code execution, server compromise
  • Mitigation: Sandbox template engines, avoid user input in templates, strict input validation

Phase 2: Authentication and Session Security

Assess authentication mechanism weaknesses:

Session Fixation (14)

  • Definition: Attacker sets victim's session ID before authentication
  • Root Cause: Session ID not regenerated after login
  • Impact: Session hijacking, unauthorized account access
  • Mitigation: Regenerate session ID on authentication, use secure session management

Brute Force Attack (15)

  • Definition: Systematic password guessing using automated tools
  • Root Cause: Lack of account lockout, rate limiting, or CAPTCHA
  • Impact: Unauthorized access, credential compromise
  • Mitigation: Account lockout policies, rate limiting, MFA, CAPTCHA

Session Hijacking (16)

  • Definition: Attacker steals or predicts valid session tokens
  • Root Cause: Weak session token generation, insecure transmission
  • Impact: Account takeover, unauthorized access
  • Mitigation: Secure random token generation, HTTPS, HttpOnly/Secure cookie flags

Credential Stuffing and Reuse (22)

  • Definition: Using leaked credentials to access accounts across services
  • Root Cause: Users reusing passwords, no breach detection
  • Impact: Mass account compromise, data breaches
  • Mitigation: MFA, breach password checks, unique credential requirements

Insecure "Remember Me" Functionality (85)

  • Definition: Weak persistent authentication token implementation
  • Root Cause: Predictable tokens, inadequate expiration controls
  • Impact: Unauthorized persistent access, session compromise
  • Mitigation: Strong token generation, proper expiration, secure storage

CAPTCHA Bypass (86)

  • Definition: Circumventing bot detection mechanisms
  • Root Cause: Weak CAPTCHA algorithms, improper validation
  • Impact: Automated attacks, credential stuffing, spam
  • Mitigation: reCAPTCHA v3, layered bot detection, rate limiting

Phase 3: Sensitive Data Exposure

Identify data protection failures:

IDOR - Insecure Direct Object References (23, 42)

  • Definition: Direct access to internal objects via user-supplied references
  • Root Cause: Missing authorization checks on object access
  • Impact: Unauthorized data access, privacy breaches
  • Mitigation: Access control validation, indirect reference maps, authorization checks

Data Leakage (24)

  • Definition: Inadvertent disclosure of sensitive information
  • Root Cause: Inadequate data protection, weak access controls
  • Impact: Privacy breaches, regulatory penalties, reputation damage
  • Mitigation: DLP solutions, encryption, access controls, security training

Unencrypted Data Storage (25)

  • Definition: Storing sensitive data without encryption
  • Root Cause: Failure to implement encryption at rest
  • Impact: Data breaches if storage compromised
  • Mitigation: Full-disk encryption, database encryption, secure key management

Information Disclosure (33)

  • Definition: Exposure of system details through error messages or responses
  • Root Cause: Verbose error handling, debug information in production
  • Impact: Reconnaissance for further attacks, credential exposure
  • Mitigation: Generic error messages, disable debug mode, secure logging

Phase 4: Security Misconfiguration

Assess configuration weaknesses:

Missing Security Headers (26)

  • Definition: Absence of protective HTTP headers (CSP, X-Frame-Options, HSTS)
  • Root Cause: Inadequate server configuration
  • Impact: XSS attacks, clickjacking, protocol downgrade
  • Mitigation: Implement CSP, X-Content-Type-Options, X-Frame-Options, HSTS

Default Passwords (28)

  • Definition: Unchanged default credentials on systems/applications
  • Root Cause: Failure to change vendor defaults
  • Impact: Unauthorized access, system compromise
  • Mitigation: Mandatory password changes, strong password policies

Directory Listing (29)

  • Definition: Web server exposes directory contents
  • Root Cause: Improper server configuration
  • Impact: Information disclosure, sensitive file exposure
  • Mitigation: Disable directory indexing, use default index files

Unprotected API Endpoints (30)

  • Definition: APIs lacking authentication or authorization
  • Root Cause: Missing security controls on API routes
  • Impact: Unauthorized data access, API abuse
  • Mitigation: OAuth/API keys, access controls, rate limiting

Open Ports and Services (31)

  • Definition: Unnecessary network services exposed
  • Root Cause: Failure to minimize attack surface
  • Impact: Exploitation of vulnerable services
  • Mitigation: Port scanning audits, firewall rules, service minimization

Misconfigured CORS (35)

  • Definition: Overly permissive Cross-Origin Resource Sharing policies
  • Root Cause: Wildcard origins, improper CORS configuration
  • Impact: Cross-site request attacks, data theft
  • Mitigation: Whitelist trusted origins, validate CORS headers

Unpatched Software (34)

  • Definition: Systems running outdated vulnerable software
  • Root Cause: Neglected patch management
  • Impact: Exploitation of known vulnerabilities
  • Mitigation: Patch management program, vulnerability scanning, automated updates

Phase 5: XML-Related Vulnerabilities

Evaluate XML processing security:

XXE - XML External Entity Injection (37)

  • Definition: Exploitation of XML parsers to access files or internal systems
  • Root Cause: External entity processing enabled
  • Impact: File disclosure, SSRF, denial of service
  • Mitigation: Disable external entities, use safe XML parsers

XEE - XML Entity Expansion (38)

  • Definition: Excessive entity expansion causing resource exhaustion
  • Root Cause: Unlimited entity expansion allowed
  • Impact: Denial of service, parser crashes
  • Mitigation: Limit entity expansion, configure parser restrictions

XML Bomb (Billion Laughs) (39)

  • Definition: Crafted XML with nested entities consuming resources
  • Root Cause: Recursive entity definitions
  • Impact: Memory exhaustion, denial of service
  • Mitigation: Entity expansion limits, input size restrictions

XML Denial of Service (65)

  • Definition: Specially crafted XML causing excessive processing
  • Root Cause: Complex document structures without limits
  • Impact: CPU/memory exhaustion, service unavailability
  • Mitigation: Schema validation, size limits, processing timeouts

Phase 6: Broken Access Control

Assess authorization enforcement:

Inadequate Authorization (40)

  • Definition: Failure to properly enforce access controls
  • Root Cause: Weak authorization policies, missing checks
  • Impact: Unauthorized access to sensitive resources
  • Mitigation: RBAC, centralized IAM, regular access reviews

Privilege Escalation (41)

  • Definition: Gaining elevated access beyond intended permissions
  • Root Cause: Misconfigured permissions, system vulnerabilities
  • Impact: Full system compromise, data manipulation
  • Mitigation: Least privilege, regular patching, privilege monitoring

Forceful Browsing (43)

  • Definition: Direct URL manipulation to access restricted resources
  • Root Cause: Weak access controls, predictable URLs
  • Impact: Unauthorized file/

Content truncated.

When not to use it

  • For real-time automated penetration testing or dynamic scanning
  • When replacing specialized security auditing tools

Prerequisites

Basic web architecture knowledgeFamiliarity with SQL/HTTPOWASP ZAP or Burp Suite

Limitations

  • Cannot detect vulnerabilities hidden by complex logic
  • Requires manual validation of findings
  • Focuses on reference data rather than live environment scanning

How it compares

It uses a structured classification framework instead of relying on generic security checklists.

Compared to similar skills

top-100-web-vulnerabilities-reference side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
top-100-web-vulnerabilities-reference (this skill)56moNo flagsIntermediate
software-security216moNo flagsIntermediate
fix-dependabot-alerts186moReviewIntermediate
backend-security-coder244moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

333868

planning-with-files

davila7

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

233106

telegram-bot-builder

davila7

Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.

106130

scroll-experience

davila7

Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.

101142

humanizer

davila7

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer

90175

game-development

davila7

Game development orchestrator. Routes to platform-specific skills based on project needs.

70195

You might also like

software-security

project-codeguard

A software security skill that integrates with Project CodeGuard to help AI coding agents write secure code and prevent common vulnerabilities. Use this skill when writing, reviewing, or modifying code to ensure secure-by-default practices are followed.

2186

fix-dependabot-alerts

microsoft

Fix Dependabot security alerts by updating vulnerable npm dependencies. Use when the user mentions "dependabot", "security alerts", "vulnerability", "CVE", or wants to update packages with security issues.

1872

backend-security-coder

sickn33

Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.

2446

equilateral-agents

Equilateral-AI

22 production-ready AI agents with database-driven orchestration for security reviews, code quality analysis, deployment validation, infrastructure checks, and compliance. Auto-activates for security concerns, deployment tasks, code reviews, quality checks, and compliance questions. Includes upgrade paths to enterprise features (GDPR, HIPAA, multi-account AWS, ML-based optimization).

564

differential-review

trailofbits

Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.

3115

security-audit

ruvnet

Comprehensive security scanning and vulnerability detection. Includes input validation, path traversal prevention, CVE detection, and secure coding pattern enforcement. Use when: authentication implementation, authorization logic, payment processing, user data handling, API endpoint creation, file upload handling, database queries, external API integration. Skip when: read-only operations on public data, internal development tooling, static documentation, styling changes.

337

Search skills

Search the agent skills registry