SSO account hijack via identity attribute mass assignment
Published Aug 18, 2026 · Updated Aug 19, 2026
Authentication bypass in RARgames 4gaBoards before 3.3.9 lets remote authenticated users misbind a victim's first SSO login. The PATCH /api/users/:id handler in server/api/controllers/users/update.js whitelists backend-managed sso* identity fields from user input, and SSO helpers such as server/api/helpers/users/get-create-one-for-github-sso.js then trust the stored provider ID for direct account lookup. Exploitation requires a normal account, a victim provider identifier, and a victim-initiated first SSO login; afterward, projects, boards, or other data that the victim creates in the attacker-owned account remain available through the attacker's original local credentials.
Summary
What happened
Authentication bypass in RARgames 4gaBoards before 3.3.9 lets remote authenticated users misbind a victim's first SSO login. The PATCH /api/users/:id handler in server/api/controllers/users/update.js whitelists backend-managed sso* identity fields from user input, and SSO helpers such as server/api/helpers/users/get-create-one-for-github-sso.js then trust the stored provider ID for direct account lookup. Exploitation requires a normal account, a victim provider identifier, and a victim-initiated first SSO login; afterward, projects, boards, or other data that the victim creates in the attacker-owned account remain available through the attacker's original local credentials.
The record
- CVE
- CVE-2026-53958
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- 4ga Labs
- Product
- 4ga Boards
- Classifications
- CWE-287, CWE-915, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=< 3.3.9
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
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