Skip to main content
VulnerabilityPublished Updated

CVE-2025-27845: Information Exposure

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 3.3.4 : patch affected systems as a priority.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.3.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

European organizations should immediately verify if they are running ESPEC North America Web Controller versions prior to 3.3.4. If so, they should prioritize upgrading to version 3.3.4 or later once available. In the absence of an official patch, organizations should implement compensating controls such as restricting network access to the /api/v4/auth/ endpoint using firewalls or network segmentation to limit exposure to trusted internal networks only. Monitoring and logging authentication attempts to detect abnormal or repeated invalid requests can help identify exploitation attempts early. Additionally, organizations should review and rotate any JWT secrets or cryptographic keys associated with the controller to invalidate potentially compromised tokens. Employing multi-factor authentication (MFA) for UI access, if supported, can add an additional security layer. Finally, conducting thorough security assessments and penetration testing on the affected systems will help identify any exploitation and verify the effectiveness of mitigations.

Description

In 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.

References

Community reviews

Loading reviews…