Vulnerability Chaining

Use when you have multiple findings and need to combine them into realistic end-to-end attack paths — turning several low/medium issues into a single critical-impact exploit chain. The red-team-lead skill that ties the specialists' findings together into business impact.

49 stars 7 forksSecurity Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add mn-youssef/security-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mn-youssef/security-skills --skill vulnerability-chaining
Manual install
git clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/vulnerability-chaining ~/.claude/skills/vulnerability-chaining

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Vulnerability Chaining (the team lead)

## Overview
Individual findings undersell real risk. Attackers don't stop at one bug — they *chain* them:
an info leak feeds an enumeration, which feeds an auth bypass, which reaches admin. This skill
takes the register from all FIND/EXPLOIT specialists and assembles attack **paths**.

**Core principle:** Chain impact is *multiplicative, not additive*. Three "Mediums" that connect
can equal one "Critical." Severity belongs to the *path*, not the isolated bug.

## ⚠️ Authorization
Demonstrate chains only on your own/authorized non-prod instance. Prove the path with the
*minimum* steps; stop at proof of impact — no persistence, no real-data exfiltration, no pivoting
to systems out of scope.

## Method
1. **Inventory primitives** — re-read every finding as a *capability*, not a label:
   - *Info* (enumeration, verbose errors, leaked ids/secrets, source maps)
   - *Foothold* (any auth bypass, XSS, SSRF, upload)
   - *Escalation* (IDOR→admin, privesc, mass assignment)
   - *Pivot* (SSRF→metadata, leaked key→cloud, token reuse)
2. **Find adjacencies** — output of one bug = precondition of another? (leaked email →
   no-rate-limit login → ATO; reflected XSS → steals admin session → admin IDOR).
3. **Build the path** — order primitives start→goal (unauth → user → admin → data/RCE).
4. **Demonstrate safely** — walk the chain end-to-end on staging, capturing each hop's PoC.
Read the full skill on GitHub

Details

Skill name
vulnerability-chaining
Path
skills/vulnerability-chaining/SKILL.md
License
MIT
Repo updated
12 June 2026

FAQ

What does the Vulnerability Chaining skill do?

Use when you have multiple findings and need to combine them into realistic end-to-end attack paths — turning several low/medium issues into a single critical-impact exploit chain. The red-team-lead skill that ties the specialists' findings together into business impact.

How do I install the Vulnerability Chaining skill?

Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Vulnerability Chaining popular?

It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.

Related skills

Access Control Testing

49

mn-youssef/security-skills

Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.

Testing & QA

Active Pentest

49

mn-youssef/security-skills

Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.

Security

API Security Testing

49

mn-youssef/security-skills

Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.

Security

Security Hierarchy Trace

49

dynamics365ninja/d365fo-cli

Trace D365FO security from a Role all the way down to Entry Points, discover which roles reach a given object, or scaffold new security objects (privilege, duty, role, XDS policy). Use when the user asks about permissions, security coverage, roles, duties, privileges, "create a security privilege", "scaffold a security role", "generate a duty", or "create a security policy".

Security26

Threat Modeling

49

mn-youssef/security-skills

Use when starting a security assessment and you need to map an application's attack surface, enumerate trust boundaries, and rank what to test first — before auditing code or running tools. Produces a prioritized target list.

Security

Security Review

32

joneqian/claude-skills-suite

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

Security

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.