Frangoteam FUXA
FUXA: JWT lifecycle flaws allow deleted or demoted users to retain privileged sessions
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In 1.3.2 and earlier, POST /api/refresh in server/api/auth/index.js falls back from current user data to decoded.groups, including when the user is deleted or groups is zero, and POST /api/heartbeat in server/api/index.js re-signs inbound JWT claims without validating the current database record. An attacker who possesses a previously issued privileged refresh cookie or access token can continue minting privileged JWTs after account deletion, disablement, role removal, or demotion. Continued refresh-cookie rotation can extend the stale session and preserve unauthorized access to user management, project manipulation, runtime configuration, scripts, and backdoor-account creation. This issue is fixed in version 1.3.3.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.3.3
Fixed in 1.3.3
Mitigation
Upgrade FUXA to 1.3.3 or later.
References
- Vendor advisory github.com/frangoteam/FUXA/security/advisories…
- Patch github.com/frangoteam/FUXA/pull/2379
- Patch github.com/frangoteam/FUXA/commit/4fa47d0a2a85…
1 more
- Release notes github.com/frangoteam/FUXA/releases/tag/v1.3.3
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.