CVE-2025-48957
📋 TL;DR
A path traversal vulnerability in AstrBot versions 3.4.4 through 3.5.12 allows attackers to access sensitive files like API keys and passwords. This affects all users running vulnerable versions of the AstrBot chatbot and development framework. The vulnerability is fixed in version 3.5.13.
💻 Affected Systems
- AstrBot
📦 What is this software?
Astrbot by Astrbot
⚠️ Risk & Real-World Impact
Worst Case
Complete compromise of LLM provider API keys, account credentials, and other sensitive configuration data leading to unauthorized access to external services and data exfiltration.
Likely Case
Information disclosure of API keys and passwords stored in configuration files, potentially enabling unauthorized use of paid LLM services or account takeover.
If Mitigated
Limited or no impact if proper network segmentation, access controls, and monitoring are in place to detect file access anomalies.
🎯 Exploit Status
The vulnerability appears to be exploitable without authentication via the dashboard interface. No public exploit code has been identified yet.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 3.5.13
Vendor Advisory: https://github.com/AstrBotDevs/AstrBot/security/advisories/GHSA-cq37-g2qp-3c2p
Restart Required: Yes
Instructions:
1. Backup your AstrBot configuration and data. 2. Stop the AstrBot service. 3. Upgrade to version 3.5.13 or later using your package manager or by downloading from the official repository. 4. Restart the AstrBot service. 5. Verify the upgrade was successful.
🔧 Temporary Workarounds
Disable Dashboard Feature
allTemporarily disable the vulnerable dashboard component by editing configuration.
Edit cmd_config.json and set dashboard-related settings to false or disable the feature
🧯 If You Can't Patch
- Implement strict network access controls to limit dashboard access to trusted IP addresses only.
- Monitor file access logs for unusual patterns of configuration file reads from the AstrBot process.
🔍 How to Verify
Check if Vulnerable:
Check if running AstrBot version between 3.4.4 and 3.5.12 inclusive, and verify dashboard feature is enabled in configuration.Check Version:
Check AstrBot version through its interface or configuration files; specific command depends on installation method.Verify Fix Applied:
Confirm AstrBot version is 3.5.13 or later and test that path traversal attempts via dashboard are properly blocked.📡 Detection & Monitoring
Log Indicators:
- Unusual file access patterns from AstrBot process to configuration files
- Failed path traversal attempts in web server logs
Network Indicators:
- HTTP requests to dashboard endpoints with path traversal patterns (../ sequences)
SIEM Query:
Search for web requests containing '../' patterns to AstrBot dashboard endpoints, or file access events from AstrBot process to sensitive configuration files.🔗 References
- https://github.com/AstrBotDevs/AstrBot/commit/cceadf222c46813c7f41115b40d371e7eb91e492
- https://github.com/AstrBotDevs/AstrBot/issues/1675
- https://github.com/AstrBotDevs/AstrBot/pull/1676
- https://github.com/AstrBotDevs/AstrBot/security/advisories/GHSA-cq37-g2qp-3c2p
- https://www.vicarius.io/vsociety/posts/cve-2025-48957-detect-astrbot-dashboard-vulnerability?prevUrl=wizard
- https://www.vicarius.io/vsociety/posts/cve-2025-48957-mitigate-astrbot-dashboard-vulnerability?prevUrl=wizard
- https://github.com/AstrBotDevs/AstrBot/security/advisories/GHSA-cq37-g2qp-3c2p
