How to fix: Slack Webhook URL Exposed
Slack webhook URL found in source.
Why it matters
Spam messages to Slack channel.
Anyone with webhook URL can post messages.
How to fix it
- 1Rotate webhook URL, keep it server-side.
Code examples
Rotate exposed Slack webhook URL
# Revoke at: api.slack.com > Your Apps > Incoming Webhooks > Revoke
# Create a new webhook URL
# Proxy Slack notifications through your own server:
# Client -> POST /api/notify -> Server uses SLACK_WEBHOOK_URL env var
# Never expose the webhook URL in client-side code or sourceReferences
Detected automatically by VulnRadar. The check id is slack-webhook-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 Slack Webhook URL Exposed?
- VulnRadar rates this medium 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 slack-webhook-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Slack Webhook URL 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.