Skip to main content
HighSecretsOWASP A07:2021CWE-798

How to fix: Cloudflare API key in source

Cloudflare API tokens look like 40-char hex strings and grant DNS / WAF / Workers access.

Why it matters

An exposed Cloudflare API token can be used to modify DNS records (pointing your domain to attacker infrastructure), disable WAF rules (exposing your origin), purge cache, or exfiltrate Workers secrets, impacting availability and security for all users of your domain.

Cloudflare API tokens look like 40-char hex strings and grant DNS / WAF / Workers access.

How to fix it

  1. 1Revoke the token in Cloudflare Dashboard → My Profile → API Tokens
  2. 2Create a new token with the minimum required zone and permission scopes
  3. 3Restrict the new token by IP allowlist and set an expiry date

Code examples

Cloudflare: create scoped token via API

bash
# Verify a token's permissions before use
curl -X GET 'https://api.cloudflare.com/client/v4/user/tokens/verify' \
  -H 'Authorization: Bearer YOUR_TOKEN'

# List all tokens to find the compromised one
curl -X GET 'https://api.cloudflare.com/client/v4/user/tokens' \
  -H 'Authorization: Bearer YOUR_TOKEN'

# Revoke it
curl -X DELETE 'https://api.cloudflare.com/client/v4/user/tokens/TOKEN_ID' \
  -H 'Authorization: Bearer YOUR_TOKEN'

Use environment variable (never hard-code)

bash
# .env (never commit)
CLOUDFLARE_API_TOKEN=your_scoped_token_here

# Read in code:
import { Cloudflare } from 'cloudflare';
const client = new Cloudflare({ apiToken: process.env.CLOUDFLARE_API_TOKEN });

References

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

See every secrets check

Questions

How severe is Cloudflare API key in source?
VulnRadar rates this high severity in the secrets 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 secret-cloudflare-api-key, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Cloudflare API key in source 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 cloudflare api key in source

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: Cloudflare API key in source | VulnRadar