/

CVE-2026-53958

Severity:

HIGH RISK

(7.6)

Mass Assignment (CWE-915) in 4gaBoards SSO Accounts

CVE-2026-53958

Deferred

Vulnerability type

Category:

Mass Assignment

CWE:

CWE-287, CWE-915

Impact:

Account takeover and unauthorized data access through SSO identity misbinding

Severity:

HIGH RISK

(7.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

4gaBoards improperly allows authenticated users to modify backend-managed single sign-on identity attributes through the user update endpoint. By associating a victim's provider identifier with an attacker-controlled account, an attacker may cause the victim's first SSO login to access the attacker's account and expose data created during that session.

Affected context

The vulnerability occurs in deployments that expose the user profile update API and permit authenticated users to submit backend-managed SSO fields. It becomes risky when provider identifiers or identity email attributes are accepted from client input and later used as trusted account-linkage keys during SSO login processing.

Exploit preconditions

  • Attack surface: Authenticated user update functionality at the user API - Required access: A valid 4gaBoards account capable of submitting profile

update requests

  • Trigger point: An SSO login flow that looks up an account using a

provider identifier

  • Why exploitation is possible: Client-controlled identity attributes are

mass-assigned and trusted before the normal email-linkage process completes

Why this happens

The underlying bug is improper control over dynamically managed attributes, corresponding to CWE-915. The user update controller includes identity fields that should be assigned only by trusted authentication workflows. Because these backend-managed attributes are accepted through a general update path, attacker-controlled values can alter the relationship between external identity providers and local accounts. Subsequent SSO lookup logic may therefore resolve a legitimate provider identity to the wrong account.

Potential impact

  • A victim may be signed into an attacker-controlled local account
  • Data created by the victim may remain accessible through the attacker's credentials
  • Projects, boards, or other account content could be exposed or modified
  • SSO account-linkage integrity could be compromised
  • Organizations may experience unauthorized access or data ownership confusion

General mitigation guidance

Mitigation generally focuses on separating user-editable profile data from authentication and identity-linkage attributes. SSO identifiers and verified email relationships should be writable only by trusted authentication workflows, not by generic user update endpoints. Allowlisting should be applied to fields based on authorization context and server-side ownership, with explicit validation of provider, identifier, and account relationships. Identity linking should require verified evidence and clear user consent. SSO and application operations should also run with least privilege, while sensitive account changes can receive additional verification and auditing.

How teams detect issues like this

Detection can include static analysis and code review rules that flag mass assignment of authentication fields, broad request-to-model updates, and client-controlled SSO identifiers. Reviewers can trace whether identity attributes are writable through general profile APIs and whether SSO lookup occurs before verified linkage checks. Runtime monitoring can alert on unexpected changes to provider identifiers, unusual account-linkage events, and identity fields being modified outside authentication workflows. Automated security review tools may help identify these patterns in controllers and model update policies.

Sources

SourceLink
github.comgithub.com/RARgames/4gaBoards/commit/7a79f4c5d338614058515752abd67e49ee2818bb
github.comgithub.com/RARgames/4gaBoards/releases/tag/v3.3.9
github.comgithub.com/RARgames/4gaBoards/security/advisories/GHSA-j2fw-r2gj-hfr3

Frequently asked

questions

It can be exploitable through the application's API by an authenticated user,

provided the deployment allows the affected profile update operation.

The attacker generally needs a valid 4gaBoards account and permission to submit

updates through the user endpoint. Administrative access should not be required.

Remove backend-managed SSO identifiers and verified identity fields from generic

update allowlists. Update them only through controlled authentication and

account-linking workflows with server-side verification.

Use field-level authorization, separate profile updates from identity management,

validate account-linkage state transitions, and audit changes to authentication

attributes.

Find out what's already
exploitable in your codebase.