T09 · Insecure Skill Coding Practices
- Location
scripts/fb_post.py:34- Finding
Facebook Access Token Exposed Through URL Query Parameters
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill performs the advertised Facebook Page posting tasks, but it handles powerful Page tokens and destructive public-content actions with weak safeguards.
Review before installing. Use a limited-scope Page token, prefer environment variables or a secure credential store over plaintext fb_config.json, rotate/revoke tokens regularly, avoid putting secrets in URLs, and manually confirm post IDs before any delete or reschedule action. Do not rely on the advertised comment-management commands unless the implementation is updated.
scripts/fb_post.py:34Facebook Access Token Exposed Through URL Query Parameters
README.md:25Mutable Unpinned Package Is Downloaded and Executed During Installation
Phần lớn mô tả khớp với hành vi thực tế: mã thực hiện đăng text/ảnh/carousel/video/Reels/story, hỗ trợ scheduled_publish_time, xem danh sách scheduled posts, xóa bài và reschedule. Tuy nhiên mô tả tuyên bố thêm các khả năng quản lý comment (comment vào bài, reply comment, xóa comment), nhưng trong mã không có endpoint, hàm, hay lệnh CLI nào liên quan đến comments. Đây là khác biệt chức năng đáng kể giữa mô tả và mã. Không thấy mã có năng lực ngoài phạm vi Facebook Page posting/management đã khai báo.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
The markdown advertises deleting scheduled posts and deleting comments as supported actions, but it does not warn that these actions can remove live content or engagement and may be irreversible. For markdown files, operations affecting user data or system integrity should include explicit warnings when such behaviors are described.
The README instructs users to run npx clawhub@latest install ..., which fetches and executes the latest package version without pinning. If the upstream package is compromised or a breaking/malicious release is published, users could unknowingly execute untrusted code during installation.
The skill documents clear network access and likely use of local configuration/secrets, but it does not declare an explicit tool scope such as allowed tools or permissions. This increases the risk of overbroad execution in an agent environment, where a loosely scoped skill could access network or environment resources beyond what users expect.
The activation text is overly broad, especially the phrase covering 'any' Facebook Page content management action. In an agent setting, broad triggers can cause the skill to activate for ambiguous requests and perform sensitive posting or management actions without sufficiently precise user intent.
The documentation includes destructive actions such as deleting posts and comments without emphasizing irreversibility or requiring confirmation. In an automated agent workflow, lack of warning around destructive operations increases the chance of accidental or unauthorized content deletion.
The documentation exposes destructive and publicly visible actions such as immediate posting, deleting posts, and deleting comments without any warning, confirmation requirement, or operator-safety guidance. In a skill that automates Facebook Page management, this increases the chance that an agent or user triggers irreversible or reputation-impacting actions without understanding they are live or destructive.
The documentation asserts that a Page Access Token is effectively 'never expires', which overstates credential permanence and can lead operators to skip rotation, expiry monitoring, and revocation planning. If the token is later invalidated due to app, user, page, or platform changes, automation may fail unexpectedly or teams may keep a powerful token indefinitely without proper lifecycle controls.
The guide tells users to store a high-privilege Page access token in a local JSON file in plaintext, with only a warning not to commit it to Git. Plaintext local secret storage increases the chance of theft through malware, backups, shared machines, accidental uploads, logs, or misconfigured file permissions, especially because this token can post and manage page content.
The script's docstrings, CLI help text, examples, status messages, and error messages are predominantly written in Vietnamese with no option to select another language. This creates a language policy issue because the skill imposes a locale on users rather than offering a choice or documenting a justified regional restriction.
The delete command performs a destructive Graph API delete immediately once a post ID is provided, with no confirmation prompt, dry-run mode, or explicit warning. In an agent/automation context, this increases the risk of accidental or prompt-induced deletion of scheduled or published content, causing integrity loss and operational disruption.