T09 · Insecure Skill Coding Practices
- Location
scripts/seo_audit.py:77- Finding
Unrestricted URL Fetching Enables Server-Side Request Forgery
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent SEO audit tool, but it encourages bypass-style fetching of protected websites and includes unrestricted URL fetching that could reach internal network resources.
Install only if you will use it on sites you own or are authorized to audit. Avoid using its WAF/bot-bypass guidance, do not scan internal or private-network URLs unless explicitly intended, and prefer user-provided HTML or source-code mode when a site blocks automated access.
scripts/seo_audit.py:77Unrestricted URL Fetching Enables Server-Side Request Forgery
The skill directs the agent to use network and shell capabilities extensively, but it does not declare an explicit tool scope such as allowed-tools or permissions. In practice, this weakens least-privilege controls and can cause agents or hosts to grant broader access than users expect, especially because the workflow includes arbitrary URL fetching and shell execution.
The skill explicitly says certain tools 'bypass WAFs/firewalls' and recommends them as the preferred path for URL fetching. Framing blocked access as a problem to overcome rather than a boundary to respect materially increases the chance that the agent will attempt unauthorized retrieval of protected resources.
This section instructs the agent to impersonate a browser User-Agent and use fallback sequencing specifically to get around bot detection and WAF-based blocking. That is dangerous because it encourages indirect circumvention of access controls on third-party sites, which can violate policy and expose the user or platform to legal, operational, or account-abuse consequences.
The troubleshooting table and notes repeatedly steer the agent toward progressively stronger anti-bot workarounds, including WebFetch preference, browser impersonation, and retry behavior after blocking responses. In context, this turns transient access failures into a playbook for circumvention, increasing the likelihood of unauthorized scraping or fetching from defended sites.
The troubleshooting guidance recommends using curl with --insecure for SSL/TLS failures, which disables certificate validation and enables man-in-the-middle interception or content spoofing. Even though it says to warn the user, the instruction still normalizes an unsafe fallback for a workflow that may influence audit conclusions and downstream code changes.
The HTTP request hard-codes Accept-Language: en-US,en;q=0.9, which imposes an English-language/US locale preference on all audited sites. This is a natural-language locale policy concern because the script does not offer the user any language/locale opt-in or explain why English is required.
The manifest describes a broader capability set that includes prioritized reports with actionable fixes and ready-to-use prompts for AI coding agents. In this file, the implementation only prints console audit sections, issue lists, and scores; aside from a single textual reference to an external template file, it does not actually generate prompts or structured remediation artifacts.
The WebPage schema example sets inLanguage to en-US, which is a natural-language locale choice presented as a default template. Because the document does not indicate this is optional or provide alternatives for other locales, it can steer users toward a fixed language/locale without explicit opt-in.
The LocalBusiness example uses addressCountry: "US" alongside a US phone format and ZIP field, which imposes a specific locale in natural-language/config content. The file does not clearly state that this locale is merely illustrative or provide guidance for non-US users.
The documentation presents the function as performing a basic structural validation, but the implementation applies narrow content requirements such as a top-level heading, blockquote summary, and a Contact section. That is more prescriptive than the docstring suggests and could mislead maintainers about what the validator is actually asserting.