T09 · Insecure Skill Coding Practices
- Location
references/worker-template.js:38- Finding
Attacker-Controlled Upstream Host Creates an Open Proxy and SSRF Primitive
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is mostly coherent for Webflow acceleration, but its Worker template grants overly broad public proxying and caching behavior that could expose private pages or be abused.
Review carefully before installing. Only use this template after adding an exact allowlist for Webflow asset hosts, disabling public caching for requests with cookies or authorization headers, honoring private/no-store origin headers, limiting R2 writes by size and content type, and removing the badge-hiding behavior unless the site owner has explicitly accepted that change.
references/worker-template.js:38Attacker-Controlled Upstream Host Creates an Open Proxy and SSRF Primitive
references/worker-template.js:157Personalized Requests Are Forwarded into Shared Public Caching
Referenced artifact was not completely inspected
完整的可直接部署的 Worker 代码见 `references/worker-template.js`。
Without declared permissions the skill's intent is opaque and cannot be validated.
The skill description is written to require this specialized skill whenever the user wants to optimize Webflow access speed in mainland China, and the file consistently presents responses/content only in Chinese. There is no indication that the user may choose another language or locale, which can violate language-choice policy when applied broadly.
This code file contains prominent natural-language documentation and usage examples exclusively in Chinese, including the top-level description and inline explanatory comments. Under the stated policy, forcing a specific language without offering user choice or documenting a justified locale constraint is a natural-language policy violation.
The worker deliberately removes and visually hides the Webflow badge, which is unrelated to China-mainland performance optimization and changes site branding/compliance behavior. Even if not directly exploitable for code execution, this is a risky overreach because it can violate platform terms, misrepresent authorship, and create trust/compliance issues outside the stated purpose of the skill.
Serving robots.txt and sitemap.xml from an R2 public endpoint is a content-hosting and SEO-related behavior rather than a direct implementation of Webflow China speed optimization. While adjacent to deployment architecture, this capability is not clearly justified by the manifest's focus on mainland access acceleration and resource proxying.
No suspicious patterns detected.