T09 · Insecure Skill Coding Practices
- Location
office_automation.py:115- Finding
Path Traversal in Batch Rename Pattern Allows Files to Be Moved Outside the Input Directory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This office automation skill appears purpose-aligned, but it can make broad local file changes with weak safeguards and unclear bounds.
Review this skill before installing. Use it only on backed-up copies of documents, avoid untrusted rename patterns, and do not run bulk replacements or renames on important folders without first testing on sample files. Treat the advertised email feature as unsupported in the inspected code unless a separate implementation is provided.
office_automation.py:115Path Traversal in Batch Rename Pattern Allows Files to Be Moved Outside the Input Directory
office_automation.py:42Unpinned Runtime Dependencies Create Supply-Chain and Reproducibility Risk
The skill advertises capabilities that would modify files, but the manifest does not declare any tool scope or permissions boundary. That makes the operational surface ambiguous and can lead users or the platform to run file-writing behavior without explicit least-privilege constraints, increasing the risk of unintended file modification.
The skill describes bulk renaming and batch document processing without warning that files may be overwritten or irreversibly changed. In this context, users may run operations across many files at once, so mistakes in patterns or replacements can cause widespread data loss or corruption.
The skill includes automated bulk email sending but does not warn that messages may be sent automatically to real recipients or that recipient data may be processed. This can cause accidental mass mailing, privacy violations, spam/compliance issues, and unintended disclosure if users run it with incorrect data or configuration.
The Word batch replacement function saves changes directly back to the original .docx files, permanently modifying user documents in place. In an automation skill, this creates a real integrity risk because a mistaken search/replace string, formatting side effect, or library parsing issue can irreversibly alter many files at once without backup, dry-run, or explicit confirmation.
Natural-language strings throughout the script, including the top-level description and command-line help, are presented only in Chinese. This can violate language/locale policy when a skill forces a specific language without user opt-in or documented regional justification.
No suspicious patterns detected.