Skip to main content
VulnerabilityPublished

CVE-2025-65027: rommapp romm · Cross-site Scripting

Affects rommapp rommSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 7.6 High : upgrade to 4.4.1 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 3 Dec 2025

  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

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 20 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 10 minutes after disclosure

  4. , 127 days after disclosure

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

What to do

Upgrade rommapp/romm to 4.4.1.

Affected software

ProductAffectedFixed in
GitHubrommapp/rommpkg:github/rommapp/rommOther threatsAffected
  • <4.4.1
  • =4.4.1-beta.2
Fixed in
  • 4.4.1

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

AI-suggested

European organizations should immediately upgrade RomM to version 4.4.1 or later to apply the vendor’s patch. In addition, implement strict server-side validation to restrict file upload types, disallowing SVG and HTML files unless absolutely necessary, and sanitize all uploaded content to prevent embedded scripts. Employ Content Security Policy (CSP) headers to limit script execution contexts and reduce XSS impact. Harden CSRF protections by ensuring anti-CSRF tokens are properly implemented and validated for all state-changing requests. Conduct regular security audits and penetration testing focusing on file upload functionalities and session management. Educate users about phishing and social engineering risks that could facilitate exploitation. Monitor logs for suspicious file uploads and unusual administrative activities. Consider network segmentation to isolate RomM servers and limit potential lateral movement in case of compromise. Finally, maintain an incident response plan tailored to web application attacks involving privilege escalation.

Description

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.

References

Community reviews

Loading reviews…