file-path-traversal-testing
Run Authorized Path Traversal Tests
Path traversal bugs can expose server files and credentials. This skill gives authorized testers a structured workflow for finding, proving, and reporting them.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "file-path-traversal-testing" from https://skillstore.io/skills/sickn33-file-path-traversal-testing.md and its manifest at https://skillstore.io/api/skills/sickn33-file-path-traversal-testing/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "file-path-traversal-testing". A tester asks for a scoped plan for a download endpoint.
Expected outcome:
A phased checklist covering authorization, parameter mapping, harmless canary tests, response comparison, stop conditions, and reporting notes.
Using "file-path-traversal-testing". A developer asks how to fix unsafe file path handling.
Expected outcome:
A remediation summary recommending strict allowlists, canonical path checks, fixed base directories, and tests for encoded traversal variants.
Using "file-path-traversal-testing". A security lead asks for evidence handling guidance.
Expected outcome:
A concise policy for minimizing sensitive data collection, redacting proof, preserving request metadata, and escalating only within written scope.
Security Audit
CriticalMost static findings are confirmed because the skill teaches actionable path traversal exploitation, sensitive file targeting, and LFI-to-RCE escalation. Markdown backtick detections are false positives, but the remaining confirmed findings show critical risk and unsafe marketplace content.
Confirmed security concerns (47)
Show all 47 confirmed findings
Capability review items (64)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (50)
๐ Network access (15)
๐ Filesystem access (47)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-file-path-traversal-testing/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-file-path-traversal-testing?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-file-path-traversal-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-file-path-traversal-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-file-path-traversal-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
sickn33. (2026). file-path-traversal-testing security audit report (audit version 5) [Author version 1.1]. Skillstore. https://skillstore.io/skills/sickn33-file-path-traversal-testing/audits/5BibTeX citation
@techreport{sickn33-sickn33-file-path-traversal-testing-2026,
author = {sickn33},
title = {file-path-traversal-testing security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-file-path-traversal-testing/audits/5},
note = {Author version 1.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "file-path-traversal-testing security audit report (audit version 5)"
version: "1.1"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-file-path-traversal-testing/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-file-path-traversal-testing:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Validate File Download Controls
Assess whether a scoped web endpoint can read files outside its intended directory.
Prepare a Penetration Test Finding
Organize evidence, impact, and remediation notes for a confirmed traversal issue.
Review Path Handling Fixes
Compare mitigations such as whitelists and canonical paths against common bypass patterns.
Try These Prompts
I have authorization to test one file download endpoint. Help me plan safe path traversal checks without accessing sensitive data.
Create a scoped path traversal test matrix for Linux and Windows targets, with expected signals and stop conditions.
Review these authorized test observations and help decide whether they prove traversal impact without exposing secrets.
Draft a professional vulnerability report with impact, affected parameters, reproduction summary, risk, and remediation guidance.
Best Practices
- Confirm written permission and scope before testing any target.
- Use harmless canary files or lab systems when proving access.
- Stop testing when secret material appears and document only necessary evidence.
Avoid
- Testing public targets without permission.
- Collecting or publishing passwords, private keys, tokens, or registry hives.
- Using RCE escalation as routine proof when file read evidence is enough.