dbcve.org
RommApplication · Romm.app

CVE-2025-65027

HIGH · 7.6 CVSS v3.1 Published 2025-12-03
Fix available
A fix is available. Upgrade to 4.4.1 or later.
See remediation →
80/100
Remediation priority · High
Remotely reachable

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
RomM (ROM Manager) allows users to scan, enrich, browse and play their game collections with a clean and responsive interface. RomM contains multiple unrestricted file upload vulnerabilities that allow authenticated users to upload malicious SVG or HTML files. When these files are accessed the browser executes embedded JavaScript, leading to stored Cross-Site Scripting (XSS) which when combined with a CSRF misconfiguration they lead to achieve full administrative account takeover, creating a rogue admin account, escalating the attacker account role to admin, and much more. This vulnerability is fixed in 4.4.1 and 4.4.1-beta.2.

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 · high confidence

RomM contains unrestricted file upload vulnerabilities allowing authenticated users to upload malicious SVG or HTML files. When these files are accessed, the browser executes embedded JavaScript, resulting in stored Cross-Site Scripting (XSS). Combined with a CSRF misconfiguration, this enables full administrative account takeover through creation of rogue admin accounts or role escalation.

MitigationUpgrade to RomM version 4.4.1 or 4.4.1-beta.2 which contains the fix. Until upgrade is possible, restrict file upload functionality to prevent SVG/HTML file uploads and implement proper content-type and file extension validation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RommApplication
Affected:< 4.4.1= 4.4.1

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:H

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. Check RomM version
    Locate the installed RomM version number in the application (typically in the frontend footer, admin panel 'About' section, package.json, or version configuration file)
    Affected if The installed version is lower than 4.4.1 or exactly equals 4.4.1 (vulnerable versions)
  2. Verify file upload capability is enabled
    Access the RomM administrative interface and check if the file upload/upload functionality for game covers or metadata is available and enabled in the settings
    Affected if File upload feature is enabled (the vulnerability requires this to be present)
  3. Inspect upload restrictions for SVG and HTML files
    Attempt to upload a test SVG or HTML file through the application's upload mechanism, or review the upload configuration/validation settings to see which file types are permitted
    Affected if SVG or HTML file extensions are accepted during upload (the XSS vector requires this)
  4. Review admin accounts for unauthorized users
    Log into the RomM administrative panel and audit the user accounts list, looking for admin accounts you did not create or unexpected role assignments
    Affected if There are admin accounts you did not create or unexpected role escalations

Your environment is affected if you are running RomM version 4.4.1 or lower AND the file upload feature is enabled and accepts SVG/HTML files.

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
Upgrade available Upgrade to 4.4.1 or later
Fixed in 4.4.1
Interim mitigation

Upgrade to RomM version 4.4.1 or 4.4.1-beta.2 which contains the fix. Until upgrade is possible, restrict file upload functionality to prevent SVG/HTML file uploads and implement proper content-type and file extension validation.

Recommended fix High confidence

RomM version 4.4.1 or 4.4.1-beta.2

  1. 1. Identify the current RomM version by checking the application or its configuration files.
  2. 2. Stop the RomM service to ensure a clean upgrade process.
  3. 3. Upgrade RomM to version 4.4.1 (stable) or 4.4.1-beta.2 (beta) using your package manager or by downloading the release from the official GitHub repository.
  4. 4. Verify the upgrade was successful by checking the new version number.
  5. 5. Restart the RomM service.
  6. 6. Test that file upload functionality properly sanitizes SVG and HTML files by uploading a benign test file.
  7. 7. If using a reverse proxy, ensure any security headers (Content-Security-Policy, X-Content-Type-Options) are properly configured.

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

Fix this in Romm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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