dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-3222

CRITICAL · 9.3 CVSS v4.0 Published 2025-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Improper Authentication vulnerability in GE Vernova Smallworld on Windows, Linux allows Authentication Abuse.This issue affects Smallworld: 5.3.3 and prior versions for Linux, and 5.3.4. and prior versions for Windows.

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

Improper Authentication vulnerability in GE Vernova Smallworld 5.3.3 (Linux) and 5.3.4 (Windows) and prior versions allows authentication abuse, potentially enabling unauthenticated or semi-authenticated attackers to bypass authentication mechanisms or misuse existing authentication to gain unauthorized access.

MitigationUpgrade Smallworld to versions beyond 5.3.3 for Linux and beyond 5.3.4 for Windows; restrict network exposure of affected systems and enforce principle of least privilege until patching is complete.

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:H/VA:H/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 installed Smallworld version
    Locate the Smallworld installation directory and check version files or use product-specific version command (e.g., sw_version, about dialog, or check installation logs)
    Affected if version is 5.3.3 or earlier on Linux, or 5.3.4 or earlier on Windows
  2. Confirm operating system platform
    Verify the host operating system where Smallworld is installed (uname -a on Linux, systeminfo on Windows)
    Affected if running Linux 5.3.3 or prior, or Windows 5.3.4 or prior versions
  3. Assess network exposure of authentication services
    Review firewall rules, network ACLs, and listening services to determine if Smallworld authentication ports (typically 80/443 for web interfaces, or custom application ports) are exposed to untrusted networks
    Affected if authentication interfaces are accessible from public or untrusted networks without VPN or IP restrictions
  4. Review authentication configuration
    Examine Smallworld authentication configuration files in the installation directory (typically under config/ or etc/ subdirectories) for settings related to authentication modes, session handling, or credential storage
    Affected if authentication is configured to allow external access or uses default settings without hardening

A system is affected if it runs Smallworld 5.3.3 or earlier on Linux, or 5.3.4 or earlier on Windows, with authentication services network-accessible to untrusted 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Smallworld to versions beyond 5.3.3 for Linux and beyond 5.3.4 for Windows; restrict network exposure of affected systems and enforce principle of least privilege until patching is complete.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3222 — 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-2025-3222 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