Skip to main content
VulnerabilityPublished Updated

CVE-2026-53959: RARgames 4gaBoards · Information Exposure

Affects RARgames 4gaBoardsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.3.9 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.3.9
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade 4gaBoards and rargames/4gaBoards to 3.3.9.

Affected software

ProductAffectedFixed in
RARgames4gaBoardsAffected
  • <3.3.9
Fixed in
  • 3.3.9
GitHubrargames/4gaBoardspkg:github/rargames/4gaBoardsOther threatsAffected
  • <3.3.9
Fixed in
  • 3.3.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade 4gaBoards to version 3.3.9 or later, where this vulnerability is fixed. The fix includes proper authorization checks and response sanitization on the affected API endpoints. No other mitigation is indicated.

Description

CVE-2026-53959 is a vulnerability in RARgames 4gaBoards prior to version 3.3.9 that allows any authenticated user to enumerate and retrieve sensitive account information of all users. The exposed data includes email addresses, phone numbers, organization details, admin status, and SSO-linked emails. This flaw arises because the API endpoints /api/users and /api/users/:id lack proper authorization checks and response sanitization. The vulnerability enables privacy breaches and facilitates targeted phishing attacks. It is fixed in version 3.3.9.

References

Community reviews

Loading reviews…