Client Side Exploitation
Use when testing advanced browser-side and HTTP-layer attacks beyond basic XSS/CSRF — DOM XSS, CSP bypass, CORS misconfiguration exploitation, postMessage abuse, prototype pollution, DOM clobbering, clickjacking, web cache poisoning, and HTTP request smuggling. On apps you own or are authorized to test.
Install
/plugin marketplace add mn-youssef/security-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add mn-youssef/security-skills --skill client-side-exploitationgit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/client-side-exploitation ~/.claude/skills/client-side-exploitationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Client-Side Exploitation (FIND/EXPLOIT — the browser & HTTP layer) ## Overview The presentation layer fails in ways scanners miss: client-side code, browser quirks, and the HTTP plumbing between the user and the server. This skill covers the advanced classes beyond the XSS/CSRF basics in `security-code-audit/references/web-frontend.md`. **Core principle:** The browser executes whatever the page tells it to, and proxies/caches trust whatever parses cleanly. Attack the *client's* trust and the *channel's* assumptions. ## Applies when / Skip when - **Applies when:** the app serves a browser-rendered UI or ships client-side JavaScript. - **Skip when:** API-only, CLI, daemon, or backend service with no browser surface → N/A. - **If N/A:** report "client-side-exploitation: N/A — no frontend surface" and stop. This is the canonical "skill doesn't match the app" case — skip cleanly, never force-fit browser tests. ## ⚠️ Authorization Your own/authorized app. Request smuggling and cache poisoning can affect *other users* of a shared cache/proxy — test only on isolated staging you control. ## Attack classes | Class | What to test | |-------|--------------| | DOM XSS | Source (`location`, `postMessage`, storage) → sink (`innerHTML`, `eval`) in client JS | | CSP bypass | Weak CSP: `unsafe-inline`, wildcards, JSONP/Angular gadgets, `base-uri` missing | | CORS exploitation | Server reflects arbitrary `Origin` + `Allow-Credentials: true` → cross-site data theft |
Details
- Skill name
client-side-exploitation- Repository
- mn-youssef/security-skills
- Path
skills/client-side-exploitation/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Client Side Exploitation skill do?
Use when testing advanced browser-side and HTTP-layer attacks beyond basic XSS/CSRF — DOM XSS, CSP bypass, CORS misconfiguration exploitation, postMessage abuse, prototype pollution, DOM clobbering, clickjacking, web cache poisoning, and HTTP request smuggling. On apps you own or are authorized to test.
How do I install the Client Side Exploitation 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 Client Side Exploitation popular?
It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.
Related skills
Access Control Testing
49mn-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.
Active Pentest
49mn-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.
API Security Testing
49mn-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.
Pentest Reporting
49mn-youssef/security-skills
Use when turning security findings into a clear, actionable report — scoring severity with CVSS, writing findings with reproduction and impact, prioritizing remediation, producing an executive summary, and tracking retests to closure. The phase that makes testing matter.
Recon and Osint
49mn-youssef/security-skills
Use when starting an assessment and you need to discover an application's full attack surface — subdomains, hosts, endpoints, technologies, exposed services, leaked credentials and secrets — on assets you own or are authorized to test. Feeds the threat model with real, not assumed, targets.
Security Code Audit
49mn-youssef/security-skills
Use when you have application source code and want to find security vulnerabilities by reading it — covers OWASP Top 10 across frontend, backend API, and database. Produces a findings register with severity, file:line, and exploitability.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.