CVE-2025-27845
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 · uneditedIn ESPEC North America Web Controller 3 before 3.3.4, /api/v4/auth/ with any invalid authentication request results in exposing a JWT secret. This allows for elevated permissions to the UI.
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 confidenceThe /api/v4/auth/ endpoint in ESPEC North America Web Controller 3 before version 3.3.4 leaks the JWT secret when processing any invalid authentication request. Attackers can capture this exposed secret and forge JWT tokens to impersonate users and gain elevated privileges to the web interface.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed versionLocate the version of ESPEC North America Web Controller installed in your environment (check product documentation for version file location or admin interface)Affected if Version is before 3.3.4
-
Verify authentication endpoint accessibilityConfirm that the /api/v4/auth/ endpoint is exposed and reachable on your Web Controller instanceAffected if Endpoint is accessible without authentication or on the internal network
-
Test for JWT secret exposureSend a crafted invalid authentication request to /api/v4/auth/ (such as malformed credentials or missing required fields) and inspect the response for any JWT secret, signing key, or token generation materialAffected if Response contains a JWT secret, signing key, or similar cryptographic material that should not be exposed
-
Compare version against affected rangeIf version identification in step 1 was successful, compare it to the affected range: versions before 3.3.4 are vulnerableAffected if Installed version is 3.3.3 or earlier
Your environment is affected if the installed version is before 3.3.4 AND the /api/v4/auth/ endpoint returns a JWT secret or signing key in response to invalid authentication requests.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to ESPEC North America Web Controller version 3.3.4 or later to obtain the patched firmware that no longer exposes the JWT secret in authentication error responses.
Upgrade to version 3.3.4 or later of ESPEC North America Web Controller 3
- Identify the current installed version of ESPEC North America Web Controller 3
- Schedule a maintenance window for the upgrade procedure
- Back up the current configuration and data of the Web Controller 3 system
- Upgrade ESPEC North America Web Controller 3 to version 3.3.4 or later
- Verify the upgrade was successful by checking the version number
- Test the /api/v4/auth/ endpoint with invalid authentication requests to confirm the JWT secret is no longer exposed
- Confirm normal authentication flow works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27845 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27845 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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