dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-55946

HIGH · 8.7 CVSS v4.0 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Playloom Engine is an open-source, high-performance game development engine. Engine Beta v0.0.1 has a security vulnerability related to data storage, specifically when using the collaboration features. When collaborating with another user, they may have access to personal information you have entered into the software. This poses a risk to user privacy. The maintainers of Playloom Engine have temporarily disabled the collaboration feature until a fix can be implemented. When Engine Beta v0.0.2 is released, it is expected to contain a patch addressing this issue. Users should refrain from using the collaboration feature in the meantime.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Playloom Engine Beta v0.0.1 contains an information disclosure vulnerability in its collaboration feature. When users collaborate with others, personal information entered into the software is improperly exposed to collaborating users due to insufficient access controls or data isolation in the collaboration data storage mechanism.

MitigationDisable or refrain from using the collaboration feature in Engine Beta v0.0.1 until upgrading to v0.0.2 when the patch is released. Avoid entering personal information into the software while collaboration remains enabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Playloom Engine Beta version
    Check the software's built-in 'About' or 'Version' menu option, or inspect the application metadata (such as the executable properties, installer details, or version file included with the installation)
    Affected if The installed version is v0.0.1 (any build of this specific version)
  2. Locate collaboration feature settings
    Access the application's main settings or preferences panel and look for sections labeled 'Collaboration', 'Share', 'Team', 'Users', or similar terms describing shared access functionality
    Affected if The collaboration feature is present and accessible in the UI or configuration files
  3. Verify collaboration is enabled
    Check the collaboration settings for an active/enabled status indicator, or examine configuration files for a flag such as 'collaboration_enabled', 'sharing_enabled', or similar boolean setting
    Affected if Collaboration sharing is turned on or configured to allow multiple users
  4. Inspect collaboration user data exposure
    Create a test collaboration session with a second user account, then observe whether personal information fields (such as name, email, profile data, or custom personal entries) entered by one user become visible to the other collaborating user without explicit sharing
    Affected if Personal information entered by one user is visible to another collaborating user who should not have access to that data

A user is affected if running Playloom Engine Beta v0.0.1 with the collaboration feature enabled, where personal data entered into the application is visible to other collaborating users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or refrain from using the collaboration feature in Engine Beta v0.0.1 until upgrading to v0.0.2 when the patch is released. Avoid entering personal information into the software while collaboration remains enabled.

Recommended fix Moderate confidence

Engine Beta v0.0.2

  1. 1. Check the current installed version of Playloom Engine (e.g., via CLI command like `playloom --version` or checking the application metadata)
  2. 2. If version is Engine Beta v0.0.1, do not use the collaboration feature until upgrade is complete
  3. 3. Download Engine Beta v0.0.2 from the official Playloom Engine repository or release page on GitHub
  4. 4. Follow the standard upgrade procedure documented for Playloom Engine (typically: backup existing project data, install the new version, verify installation)
  5. 5. After upgrading to v0.0.2, verify the collaboration feature has been re-enabled and is functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-55946 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-55946 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data