File Upload and Ssrf
Use when testing file-upload handling, server-side request forgery (SSRF), and insecure deserialization — upload bypasses (type/extension/content, polyglots, path traversal), SSRF to cloud metadata and internal services, and unsafe deserialization sinks. 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 file-upload-and-ssrfgit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/file-upload-and-ssrf ~/.claude/skills/file-upload-and-ssrfPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# File Upload, SSRF & Deserialization (FIND/EXPLOIT — server input handling) ## Overview Three high-impact classes that often reach RCE or full cloud compromise and were previously homeless across the references: untrusted **files**, untrusted **URLs**, and untrusted **serialized objects**. All three are "the server processes attacker-supplied data." **Core principle:** Anywhere the server *fetches*, *stores+serves*, or *reconstructs* attacker data, ask what else it can be pointed at or made into. ## Applies when / Skip when - **Applies when:** the app accepts **file uploads**, **fetches user-supplied URLs**, or **deserializes** input — test each of the three independently. - **Skip when:** a given feature is absent → that part is N/A (e.g. no uploads → skip the upload section but still test SSRF/deserialization if present). - **If N/A:** report which of the three are absent and test only what exists. ## ⚠️ Authorization Your own/authorized non-prod. SSRF can reach real internal infra and cloud creds — keep targets to your environment; use benign canaries, don't pivot out of scope. ## File upload | Check | Test | |-------|------| | Type/extension bypass | `shell.php.jpg`, double ext, null byte, case, `.phtml`/`.svg`/`.htaccess` | | Content-type spoof | Real image bytes + script; mismatched `Content-Type` header | | Polyglot | File valid as image **and** script (e.g. GIF/PHP) | | Path traversal | Filename `../../var/www/shell.php` to control where it lands |
Details
- Skill name
file-upload-and-ssrf- Repository
- mn-youssef/security-skills
- Path
skills/file-upload-and-ssrf/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the File Upload and Ssrf skill do?
Use when testing file-upload handling, server-side request forgery (SSRF), and insecure deserialization — upload bypasses (type/extension/content, polyglots, path traversal), SSRF to cloud metadata and internal services, and unsafe deserialization sinks. On apps you own or are authorized to test.
How do I install the File Upload and Ssrf 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 File Upload and Ssrf 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.
Injection Testing
49mn-youssef/security-skills
Use when dynamically testing whether untrusted input reaches an interpreter — SQL/NoSQL injection (incl. blind/time-based), OS command injection, server-side template injection (SSTI), XXE, LDAP/XPath, and CRLF/header injection. Confirms on a running app what security-code-audit finds in source.
Business Logic Testing
49mn-youssef/security-skills
Use when testing application-specific workflow and business-rule flaws that scanners cannot find — price/quantity/parameter tampering, workflow and state-machine bypass, race conditions and TOCTOU, replay, and abuse of coupons/refunds/limits. Requires understanding what the app is supposed to do.
Spec Driven Test
32Loveforwa/spec-test.skill
Use specification-based testing methodology for end-to-end testing of web applications. Use this skill when users request "test this feature", "check this feature completeness", "do E2E testing on this project", "test this web app with an agent", or directly mention spec-driven-test / specification-based testing. This skill also applies to scenarios where users want to automatically generate test specs and test cases from code, then execute tests through browser automation. Even if users don't explicitly mention "spec" or "test case", if they want to systematically and automatically test a spe
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.