Unauthenticated data disclosure via guest-context token fallback
Published Aug 12, 2026 · Updated Aug 12, 2026
Authentication bypass in Frangoteam FUXA 1.3.0-2773 allows remote attackers to read project, alarm, and scheduler data over HTTP. The verifyToken() path in server/api/jwt-helper.js converts a missing or invalid token into guest context, and three read handlers accept that context instead of rejecting it. Exploitation requires secureEnabled=true and exposes project metadata, alarms, and scheduler information without credentials.
Summary
What happened
Authentication bypass in Frangoteam FUXA 1.3.0-2773 allows remote attackers to read project, alarm, and scheduler data over HTTP. The verifyToken() path in server/api/jwt-helper.js converts a missing or invalid token into guest context, and three read handlers accept that context instead of rejecting it. Exploitation requires secureEnabled=true and exposes project metadata, alarms, and scheduler information without credentials.
The record
- CVE
- CVE-2026-47718
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Frangoteam
- Product
- FUXA
- Classifications
- CWE-287, CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 1.3.0-2773
What conditions does exploitation require?
What is affected?
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
- GHSA guest and invalid-token HTTP reproduction procedureproof of concept · demonstrated
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