How to fix: Firebase Configuration Exposed
Firebase configuration object found in page source.
Why it matters
While Firebase keys are designed to be public, exposed config may indicate unsecured backend rules.
Firebase config is semi-public but should be paired with security rules.
How to fix it
- 1Ensure Firestore/RTDB security rules are properly configured.
Code examples
Firebase config is public by design: secure with App Check + RLS
// Firebase web config (apiKey, projectId, etc.) is INTENTIONALLY public
// Security depends on Firestore Security Rules and App Check
// Enable App Check:
import { initializeAppCheck, ReCaptchaV3Provider } from "firebase/app-check";
initializeAppCheck(app, {
provider: new ReCaptchaV3Provider(process.env.NEXT_PUBLIC_RECAPTCHA_KEY!),
isTokenAutoRefreshEnabled: true,
});
// Ensure Firestore rules require authentication:
// match /{doc=**} { allow read, write: if request.auth != null; }References
Detected automatically by VulnRadar. The check id is firebase-config-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 Firebase Configuration 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 firebase-config-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Firebase Configuration 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.