dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-32138

HIGH · 8.2 CVSS v3.1 Published 2026-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NEXULEAN is a cybersecurity portfolio & service platform for an Ethical Hacker, AI Enthusiast, and Penetration Tester. Prior to 2.0.0, a security vulnerability was identified where Firebase and Web3Forms API keys were exposed. An attacker could use these keys to interact with backend services without authentication, potentially leading to unauthorized access to application resources and user data. This vulnerability is fixed in 2.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NEXULEAN versions prior to 2.0.0 exposed Firebase and Web3Forms API keys in client-side code. These hardcoded credentials allowed unauthenticated attackers to interact with backend services, potentially accessing application resources and user data.

MitigationUpdate to version 2.0.0 or later, rotate all exposed API keys immediately, and migrate sensitive credentials to server-side environment variables or a secrets management solution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check NEXULEAN platform version
    Locate the version identifier in your installation (typically in package.json, version file, or admin interface). Compare it to the affected range: versions prior to 2.0.0 are vulnerable.
    Affected if Installed version is lower than 2.0.0
  2. Inspect client-side source code for Firebase credentials
    Search frontend source files (JavaScript, TypeScript, HTML templates) for Firebase-related strings such as 'firebaseConfig', 'apiKey', or patterns matching 'AIza...' which are typical Firebase API key formats. Also check minified/bundled JavaScript files in the webroot.
    Affected if Any hardcoded Firebase API key (apiKey field) or configuration containing 'firebase' is found in client-accessible code
  3. Inspect client-side source code for Web3Forms credentials
    Search frontend source files for Web3Forms-related strings such as 'Web3Forms', 'access_key', or any access key strings that correspond to the Web3Forms service. Check both source and bundled files.
    Affected if Any hardcoded Web3Forms access_key is found in client-accessible code
  4. Verify credentials are exposed in browser-accessible resources
    Load the application in a browser, open developer tools, and examine the Network tab or view-page-source to check if API keys are present in loaded JavaScript files, inline scripts, or network responses.
    Affected if API keys are visible when viewing the page source or in browser developer tools

A user is affected if their NEXULEAN installation version is below 2.0.0 AND hardcoded Firebase or Web3Forms API keys are discoverable in client-side code or browser-accessible resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.0.0 or later, rotate all exposed API keys immediately, and migrate sensitive credentials to server-side environment variables or a secrets management solution.

Recommended fix High confidence

2.0.0

  1. 1. Identify the current version of NEXULEAN platform installed in your environment
  2. 2. If the current version is before 2.0.0, backup all application data and configurations
  3. 3. Update the NEXULEAN application to version 2.0.0 or later
  4. 4. After upgrading, verify that Firebase and Web3Forms API keys are no longer exposed in the application
  5. 5. Rotate the exposed Firebase and Web3Forms API keys as a precautionary measure to prevent any potential unauthorized access from keys that may have been compromised prior to the upgrade
  6. 6. Test the application functionality to ensure the upgrade did not introduce any regressions
Caveat Review release notes for 2.0.0 to check for any breaking changes in functionality or configuration

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32138 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data