T09 · Insecure Skill Coding Practices
- Location
mx_select_stock.py:223- Finding
Unsanitized API Data Enables CSV Formula Injection
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent stock-screening API tool, with expected network use and local result files, but users should treat generated CSV data as untrusted.
Install only if you are comfortable sending stock-screening query text to Eastmoney's Miaoxiang API using MX_APIKEY. Keep sensitive information out of queries, review the output directory for retained CSV/description/raw JSON files, and open generated CSVs with spreadsheet formula execution disabled or after sanitizing untrusted values.
mx_select_stock.py:223Unsanitized API Data Enables CSV Formula Injection
The skill advertises capabilities that involve environment-variable access, network access, and local file writes, but it does not declare any explicit tool scope such as permissions or allowed-tools. This creates an authorization ambiguity where an agent may invoke broader capabilities than a user expects, increasing the risk of unintended data access, external requests, or filesystem modification.
The skill sends the user-provided query and an API key to an external third-party endpoint. While external API access is expected for this skill's purpose, it still creates a real data exposure risk because any sensitive information embedded in the query will be transmitted outside the local environment and persisted in returned/output files.
"keyword": query
}
response = requests.post(self.BASE_URL, headers=headers, json=data, timeout=30)
response.raise_for_status()
return response.json()
The skill states that it will automatically create an output directory and write result files, but it does not clearly warn users about the local side effects or give them control over whether persistence occurs. While the described writes appear related to normal functionality, undisclosed automatic filesystem changes can leak sensitive query content into local storage and surprise downstream users or agents.
The file’s natural-language descriptions and examples are entirely in Chinese, including the skill name and usage guidance, with no indication that another language is supported or that the user may choose their preferred language. Under the policy, forcing a specific language without opt-in is a natural-language policy concern.
No suspicious patterns detected.