file-access-vuln

Route file access and upload issues to the correct security testing path.

11|4|Updated Jun 7, 2026

Search Tags:#routing #security testing #file upload #file access #lfi #path traversal

Ready to run

npx skills add https://github.com/sayseven7/frameseven --skill file-access-vuln-sayseven7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: file-access-vuln
Source: https://github.com/sayseven7/frameseven/tree/main/internal/mcp/skills/file-access-vuln
Command: npx skills add https://github.com/sayseven7/frameseven --skill file-access-vuln-sayseven7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you decide whether a file-related entry point is a path traversal or local file inclusion issue, or whether it belongs to an upload validation and processing chain problem.

Core Features & Use Cases

Entry-point routing: Identifies whether the target behavior is driven by a path parameter, download endpoint, upload flow, preview pipeline, archive extraction, or shared storage boundary.
Security triage: Separates file read and path traversal concerns from upload acceptance, storage, processing, and serving risks.
Use case: If an application lets users upload files and later preview or download them, this Skill helps route the assessment to the correct follow-on testing workflow.

Quick Start

Use this Skill to classify the file-related workflow and determine whether the next step should be path traversal testing or insecure upload testing.

Frequently Asked Questions about file-access-vuln

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I distinguish between path traversal and local file inclusion vulnerabilities in a file endpoint?▼

Path traversal risks involve manipulating path parameters or download endpoints to access restricted files, while local file inclusion targets preview chains and archive extraction workflows. This Skill routes file access issues by separating read concerns from upload processing risks.

What is the best way to triage file upload validation issues during security testing?▼

Triage upload validation issues by breaking the workflow into accept, store, process, and serve stages. This approach isolates insecure upload risks like storage boundary violations from file read and path traversal concerns during security testing.

How do I test path traversal risks in download endpoints and path parameters?▼

Test path traversal in download endpoints by routing file access issues to the correct evaluation path. This distinguishes path parameter manipulation from upload validation chains, ensuring traversal risks are assessed consistently across shared storage boundaries.

When do I need to separate file read concerns from upload processing risks?▼

Separate file read concerns from upload processing risks when an application lets users upload files and later preview or download them. This distinction ensures path traversal and local file inclusion risks are evaluated independently from insecure upload validation.

Does this security testing approach work for archive extraction and preview pipelines?▼

Yes, this security testing approach works for archive extraction and preview pipelines by routing file access issues to the correct evaluation path. It classifies entry points to determine whether path traversal or insecure upload testing should follow.