How to fix: Discord Webhook URL Exposed
A Discord incoming webhook URL was found in page source.
Why it matters
Anyone with the webhook URL can post arbitrary messages (spam, phishing links, impersonation) to the Discord channel it's bound to.
Discord webhook URLs are bearer credentials -- possession of the URL is sufficient to post to the channel, with no further authentication.
How to fix it
- 1Delete and regenerate the webhook in Discord's Integrations settings.
- 2Move webhook calls server-side behind your own API endpoint instead of calling Discord directly from the browser.
Code examples
Move Discord webhook URL to a server-side environment variable
// BAD: webhook URL in client-side code or source
// fetch("https://discord.com/api/webhooks/ID/TOKEN", ...)
// GOOD: proxy through your own API endpoint
// Client:
await fetch("/api/notify", { method: "POST", body: JSON.stringify({ message }) });
// Server route (uses env var, not exposed to client):
export async function POST(req: Request) {
await fetch(process.env.DISCORD_WEBHOOK_URL!, {
method: "POST",
body: JSON.stringify({ content: (await req.json()).message }),
headers: { "Content-Type": "application/json" },
});
return Response.json({ ok: true });
}References
Detected automatically by VulnRadar. The check id is discord-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 Discord 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 discord-webhook-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Discord Webhook URL Exposed map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05: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.