T09 · Insecure Skill Coding Practices
- Location
url-to-markdown/mp.weixin.qq.com/page.md:2- Finding
Plaintext URL Token Stored in Captured Content
- Content
View full analysis
Vulnerability Details
File Location:
url-to-markdown/mp.weixin.qq.com/page.md, line 2
Vulnerability Type: Plaintext exposure of token-like URL data
Risk Level: LowVulnerable Code
yaml url: https://mp.weixin.qq.com/s/9zw_m0pwL0pzOy_8efy_aQ?poc_token=HHx0smmjqqNTpt4KMwjMSd1ae1ZrbcnqNQj0S_8gTechnical Analysis
The captured page metadata stores a
poc_tokenquery parameter in plaintext. URL query parameters may be copied into repositories, logs, generated documents, browser history, analytics systems, and downstream exports. If this value provides access control or request validation and remains valid, anyone who can read the project could attempt to replay it.Static analysis cannot establish whether the token is currently valid, secret, or privileged. The finding is therefore rated Low, but the value should still be treated as potentially sensitive and removed according to secure data-handling practices.
Attack Path
- An attacker obtains read access to the project or a derived artifact.
- The attacker opens
url-to-markdown/mp.weixin.qq.com/page.md. - The attacker extracts the
poc_tokenvalue from line 2. - The attacker replays the complete URL in a request to the remote service.
- If the token remains valid and conveys access, the service returns the associated resource or permits whatever operation the token authorizes.
This path is conditional on the remote service accepting the token and the token conferring access.
Impact Assessment
The maximum obtainable privileges cannot be determined from the repository alone. Plausible impact is limited to the remote resource or request scope authorized by the exposed token. No evidence indicates local code execution, host compromise, privilege escalation, persistence, or broader account access.
- Remediation
View remediation
Remediation Suggestions
- Remove the query string and retain only the canonical article URL:
yaml url: https://mp.weixin.qq.com/s/9zw_m0pwL0pzOy_8efy_aQ - Revoke or rotate the exposed token if the remote service supports doing so.
- Review repository history and generated artifacts for retained copies, removing them where practical.
- Add URL sanitization to the capture process so sensitive parameters such as tokens, signatures, session identifiers, and access keys are stripped before content is persisted.
- Maintain an allowlist of query parameters that are safe to retain rather than relying only on a denylist.
- Add secret scanning to the commit or publication workflow to detect token-like query parameters.
- Remove the query string and retain only the canonical article URL:
