How to fix: Twilio Account SID Exposed
A Twilio Account SID pattern was found in the page. The Account SID functions like a username, not a secret, and Twilio's own docs describe it as safe to share; it grants no API access without the paired Auth Token.
Why it matters
Low on its own. Verify the paired Auth Token or API Key Secret isn't also exposed nearby; only that combination grants API access.
Twilio Account SIDs are routinely displayed for reference (client-side SDK setup, webhook configuration pages). Only the Auth Token or an API Key Secret is a real credential.
How to fix it
- 1Confirm no Auth Token or API Key Secret is exposed alongside this SID; rotate immediately if one is found.
Code examples
Rotate exposed Twilio credentials
# Rotate Auth Token: console.twilio.com > Settings > API Keys
# Or rotate the Account SID secondary auth token
# Check for unauthorized SMS/calls:
# GET /2010-04-01/Accounts/ACXXXXXX/Messages
# Store credentials server-side only:
# TWILIO_ACCOUNT_SID=AC...
# TWILIO_AUTH_TOKEN=your_tokenReferences
Detected automatically by VulnRadar. The check id is twilio-credentials-exposed, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Twilio Account SID Exposed?
- VulnRadar rates this low severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id twilio-credentials-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Twilio Account SID Exposed map to?
- It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.