Skip to main content
HighContentOWASP A07:2021CWE-798

How to fix: SendGrid API Key Exposed

SendGrid API key pattern found.

Why it matters

Email sending abuse, phishing.

SendGrid keys allow email sending.

How to fix it

  1. 1Rotate API key immediately.

Code examples

Rotate exposed SendGrid API key

bash
# Revoke at: app.sendgrid.com > Settings > API Keys
# Create a new key with minimum required permissions (Mail Send only)

# Never expose the SendGrid key in client-side code
# Proxy email sending through your own API route:
# POST /api/send-email (server-side, uses SENDGRID_API_KEY env var)

References

Detected automatically by VulnRadar. The check id is sendgrid-key-exposed, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is SendGrid API Key Exposed?
VulnRadar rates this high 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 sendgrid-key-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does SendGrid API Key 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.

Propose a checkHow a check is built

Scan your own site for sendgrid api key exposed

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: SendGrid API Key Exposed | VulnRadar