Description
4gaBoards is a boards system for realtime project management. Prior to 3.3.9, 4gaBoards allows an authenticated user to modify ssoGoogleId, ssoGoogleEmail, ssoGithubId, ssoGithubUsername, ssoGithubEmail, ssoMicrosoftId, ssoMicrosoftEmail, ssoOidcId, and ssoOidcEmail through PATCH /api/users/:id. The whitelist in server/api/controllers/users/update.js mass assigns these backend-managed identity attributes from user input. An attacker can place a victim's provider identifier on an attacker-controlled account, causing the default lookup in helpers such as server/api/helpers/users/get-create-one-for-github-sso.js to match the victim's first SSO login to the attacker's account before the email-linkage flow runs. The victim is logged into the attacker-controlled account, and projects, boards, or data the victim creates remain accessible through the attacker's original local credentials. This issue is fixed in version 3.3.9.
Published: 2026-08-18
Score: 7.6 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

4gaBoards allows an authenticated user to modify SSO identity attributes through the PATCH /api/users/:id endpoint without proper authorization checks. This mass assignment flaw lets an attacker place a victim’s provider identifier on an attacker‑controlled account, causing the system’s default lookup to bind the victim’s first SSO login to the attacker’s account before the normal email‑linkage process runs. As a result the victim is inadvertently logged into the attacker’s account and any projects or data the victim creates remain accessible via the attacker’s credentials. The weakness is captured by CWE‑287 and CWE‑915.

Affected Systems

The vulnerability affects the RARgames 4gaBoards application, versions prior to 3.3.9. The official fix is included in release 3.3.9, which removes the mass assignment of the listed SSO attributes.

Risk and Exploitability

The CVSS score of 7.6 places this issue in the high‑severity range, while the EPSS score is unavailable and it is not listed in the CISA KEV catalog. Exploitation requires an authenticated user to send a crafted PATCH request to another user’s endpoint; no special local privilege or network restrictions are mentioned, implying a remote attack vector once a user is logged in. Because the flaw directly enables a pre‑account takeover, the likelihood of impact is significant, especially in environments where users have unrestricted access to the full update endpoint.

Generated by OpenCVE AI on August 18, 2026 at 22:47 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Deploy 4gaBoards version 3.3.9 or later to eliminate the mass assignment flaw.
  • Configure the PATCH /api/users/:id handler to whitelist only allowed fields and explicitly prohibit changing any SSO identity attributes for users other than the authenticated requester.
  • Review and restrict any administrative roles that allow unrestricted user updates, ensuring least‑privilege for accounts that can call the update endpoint.
  • Monitor application logs for abnormal PATCH activity or unsolicited changes to SSO identifiers as a detection measure.

Generated by OpenCVE AI on August 18, 2026 at 22:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 18 Aug 2026 23:00:00 +0000

Type Values Removed Values Added
First Time appeared Rargames
Rargames 4gaboards
Vendors & Products Rargames
Rargames 4gaboards

Tue, 18 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
Description 4gaBoards is a boards system for realtime project management. Prior to 3.3.9, 4gaBoards allows an authenticated user to modify ssoGoogleId, ssoGoogleEmail, ssoGithubId, ssoGithubUsername, ssoGithubEmail, ssoMicrosoftId, ssoMicrosoftEmail, ssoOidcId, and ssoOidcEmail through PATCH /api/users/:id. The whitelist in server/api/controllers/users/update.js mass assigns these backend-managed identity attributes from user input. An attacker can place a victim's provider identifier on an attacker-controlled account, causing the default lookup in helpers such as server/api/helpers/users/get-create-one-for-github-sso.js to match the victim's first SSO login to the attacker's account before the email-linkage flow runs. The victim is logged into the attacker-controlled account, and projects, boards, or data the victim creates remain accessible through the attacker's original local credentials. This issue is fixed in version 3.3.9.
Title 4gaBoards: SSO Pre-Account Takeover / Hijacking via Mass Assignment
Weaknesses CWE-287
CWE-915
References
Metrics cvssV3_1

{'score': 7.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L'}


Subscriptions

Rargames 4gaboards
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-18T21:34:59.454Z

Reserved: 2026-06-11T15:50:01.282Z

Link: CVE-2026-53958

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-18T22:16:54.717

Modified: 2026-08-18T22:16:54.717

Link: CVE-2026-53958

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T23:00:14Z

Weaknesses
  • CWE-287

    Improper Authentication

  • CWE-915

    Improperly Controlled Modification of Dynamically-Determined Object Attributes