T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:114- Finding
Submission, OAuth, and File-Upload Operations Exceed the Skill's Declared Scope
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill claims submission is out of scope but then instructs agents to submit forms, upload files, use OAuth, store credentials, and create GitHub pull requests.
Review this carefully before installing. The local parsing and classification pieces are coherent, but the submission sections should be removed or split into a separate explicitly authorized skill. Do not run bulk submission, use OAuth sessions, upload files, create GitHub PRs, or store real passwords in project JSON without per-site review and explicit approval.
SKILL.md:114Submission, OAuth, and File-Upload Operations Exceed the Skill's Declared Scope
SKILL.md:196Plaintext Credential Fields May Be Stored and Sent to Untrusted Submission Targets
The manifest explicitly says submission is out of scope, but the rest of the document instructs submission via automation, manual browser interaction, and GitHub PRs. This inconsistency is dangerous because policy or routing systems may trust the manifest while the body quietly grants more powerful behaviors.
The skill’s body expands from updating a local JSON file into discovering forms and submitting data to third-party sites, directly contradicting the manifest’s stated scope. This is dangerous because an agent selecting the skill for a low-risk data maintenance task could be induced into making external side effects, including submissions, browser interactions, and account-related actions the user did not explicitly authorize.
The automated/manual submission section authorizes actions such as filling forms, uploading files, handling OAuth flows, and clicking submit, which are unrelated to the declared task of adding entries to directories.json. That mismatch creates a capability-escalation risk where a seemingly administrative skill can perform real-world external actions on third-party services.
Authorizing use of the gh CLI to clone repositories and potentially operate on curated lists is broader than necessary for simple parsing of provided inputs. While cloning public repos is not inherently dangerous, adding repository-manipulation guidance in a data-ingestion skill increases the chance of unnecessary credential use and scope creep.
The skill instructs making external changes—submissions, uploads, and button clicks on third-party sites—without an upfront warning that these actions have side effects outside the local repository. In agentic settings, lack of explicit user warning and confirmation can lead to unintended postings, account use, or data disclosure.
Including GitHub fork/clone/branch/push/PR instructions extends the skill from local data curation into modifying external repositories. Even if framed as optional, this broadens the agent’s authority and can cause unintended public changes under the operator’s credentials.
No suspicious patterns detected.