T09 · Insecure Skill Coding Practices
- Location
scripts/skill_router.py:50- Finding
API Key Disclosure Through Cross-Origin HTTP Redirects
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears to be a legitimate Media.io Kling video-generation wrapper, but it needs review because it under-discloses third-party media handling and has an API-key redirect containment gap.
Review before installing. Use a dedicated low-privilege or low-credit Media.io API key, avoid submitting sensitive private media or confidential prompts, confirm Media.io billing and retention terms, and prefer a patched router that sets allow_redirects=False for authenticated requests.
scripts/skill_router.py:50API Key Disclosure Through Cross-Origin HTTP Redirects
The motion-control endpoint accepts both video and image inputs and sends them to an external generation service, yet the documentation lacks any warning about off-platform transmission. Because richer media inputs can contain sensitive visual data, this creates elevated privacy and confidentiality risk if users submit internal, personal, or proprietary content without informed consent.
The skill instructs users to supply an API key and send requests to a third-party service, but it does not disclose that prompts, source images, generated media, and usage metadata may be transmitted to Media.io and may incur costs. This creates a real security and privacy risk because users may unknowingly expose sensitive content or trigger billable API usage without informed consent.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"description": "API to query user credits balance.",
"api_header": "{\"list\": [{\"name\": \"X-API-KEY\", \"value\": \"API key to authorize requests\"}, {\"name\": \"Content-Type\", \"value\": \"application/json\"}], \"title\": \"Authorizations\", \"describe\": \"Add the following authorization information in the request header\"}",
"api_body": "{\"title\": \"Request Body\", \"category\": [{\"list\": [], \"title\": \"Query Credits\", \"describe\": \"Request body to query user credits balance\"}]}",
"api_request_demo": "{\"title\": \"Example Request\", \"request\": [{\"title\": \"Query User Credits\", \"language\": \"cURL\", \"code_example\": \"curl --request POST \\n --url https://openapi.media.io/user/credits \\n --header 'Content-Type: application/json' \\n --header 'X-API-KEY: <api-key>' \\n --data '{}'\"}]}",
"api_response": "{\"list\": [{\"name\": \"code\", \"type\": \"integer\", \"describe\": \"Response status code, 0 indicates success\"}, {\"name\": \"msg\", \"type\": \"string\", \"describe\": \"Response message, empty string on success\"}, {\"name\": \"data\", \"type\": \"object\", \"describe\": \"Response data object\"}, {\"name\": \"credits\", \"type\": \"integer\", \"describe\": \"User credits balance, located within the data object\"}], \"title\": \"Response\", \"describe\": \"After the request is successfully processed, the server will return the following response\"}",
"api_code_demo": "{\"list\": [{\"code\": \"0\", \"describe\": \"Success\"}, {\"code\": \"40001\", \"describe\": \"Invalid API key\"}, {\"code\": \"40002\", \"describe\": \"API key expired\"}], \"title\": \"Status Code\"}",
"content": null,
The documentation instructs users to submit image URLs to a third-party external API without any notice that user-provided media references will be transmitted off-platform. In a skill context, this can lead to unintended disclosure of private or sensitive media locations, especially if users assume processing is local or first-party.
This API supports prompt-driven media generation with optional audio generation, but the documentation does not warn that prompts and referenced content are sent to an external service. Users may unknowingly disclose sensitive prompts, copyrighted material references, or private content when invoking the skill.
The entry's name and endpoint clearly describe a motion-control variant (Motion Control Kling 2.6 and i2v-motion-control-kling-v2-6), while the title says Kling 2.6 API Documentation. This is an active documentation contradiction that could mislead consumers about which model/capability this record represents.