Most static findings are false positives from Markdown examples, JSON-LD templates, placeholder URLs, and words containing key. Real risks remain from outbound website audits, DataForSEO API communication, and environment-based API credentials. No prompt-injection evidence was found.
The helper reads DataForSEO credentials from environment variables. This is intended, but it gives the skill access to user-provided API secrets when scripts run.
The helper reads DataForSEO credentials from environment variables. This is intended, but it gives the skill access to user-provided API secrets when scripts run.
The DataForSEO wrapper makes outbound HTTPS requests to the documented API endpoint. This network access is expected for keyword research, but it is real third-party communication.
The DataForSEO wrapper makes outbound HTTPS requests to the documented API endpoint. This network access is expected for keyword research, but it is real third-party communication.
with urllib.request.urlopen(req, timeout=60) as resp:
The DataForSEO wrapper makes outbound HTTPS requests to the documented API endpoint. This network access is expected for keyword research, but it is real third-party communication.
The DataForSEO wrapper makes outbound HTTPS requests to the documented API endpoint. This network access is expected for keyword research, but it is real third-party communication.
The SEO audit script uses urllib to fetch a target page and related crawl files. The behavior is intended, but it performs outbound requests from the runtime environment.
The SEO audit script uses urllib to fetch a target page and related crawl files. The behavior is intended, but it performs outbound requests from the runtime environment.
with urllib.request.urlopen(req, timeout=timeout) as resp:
The SEO audit script uses urllib to fetch a target page and related crawl files. The behavior is intended, but it performs outbound requests from the runtime environment.
The audit script accepts a URL argument and fetches that page, then derives robots.txt and sitemap.xml URLs from the same host. Without host validation, running it in a privileged agent environment could reach internal services or attacker-controlled hosts.
The code directly uses user-provided URL input in urllib requests and derives additional URLs from that host. This is intentional SEO behavior, but the absence of host controls creates SSRF-style risk.
04
是正措置
この監査で推奨される修正が記録されています。これらを適用する責任はメンテナーにあります。
FIX-001
中
The SEO audit script can fetch arbitrary user-supplied URLs.
Validate URL schemes and hosts, block localhost and private IP ranges, limit redirects, and cap response size before fetching.
FIX-002
中
A schema template includes a curl pipe-to-shell install example as placeholder text.
Replace the install text with neutral signup guidance or a safer installation example that does not pipe remote content into a shell.
FIX-003
低
DataForSEO scripts read API credentials from environment variables and send requests to a third-party API.
Document the outbound API use clearly, require explicit user consent before running paid API scripts, and recommend least-privilege credentials.
FIX-004
低
Command examples can trigger network requests when copied or executed by an agent.
Mark command examples as optional, require target-domain confirmation, and remind users to run them only for authorized sites.