Post-logout session access via unrevoked JWT
Published Aug 14, 2025 · Updated Aug 15, 2025
Improper session termination in ESPEC North America Web Controller 3.0.0 through 3.3.7 allows attackers to reuse JWTs after logout. The /api/v4/auth/ logout path leaves issued JWTs valid because affected firmware does not remove them from an authorization whitelist. Possession of a previously issued JWT is required and preserves the associated account's session privileges after logout.
Summary
What happened
Improper session termination in ESPEC North America Web Controller 3.0.0 through 3.3.7 allows attackers to reuse JWTs after logout. The /api/v4/auth/ logout path leaves issued JWTs valid because affected firmware does not remove them from an authorization whitelist. Possession of a previously issued JWT is required and preserves the associated account's session privileges after logout.
The record
- CVE
- CVE-2025-27847
- Published
- Aug 14, 2025
- Updated
- Aug 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1550.001
- Attack vector
- Unavailable
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 14, 2025CVE publishedPublication date reported by the CVE source.
- Aug 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo