Skip to main content
CVE-2025-65097VulnerabilityPublished

CVE-2025-65097: rommapp romm · Improper Access Control

Affects rommapp rommSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High : upgrade to 4.4.1 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.4.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  5. 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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

1. Upgrade RomM to version 4.4.1 or later, where the vulnerability is patched with proper ownership verification. 2. Implement strict access control policies at the application and network layers to restrict DELETE requests to authorized users only. 3. Monitor application logs for unusual DELETE request patterns or attempts to access collections not owned by the requester. 4. Enforce strong authentication mechanisms and consider multi-factor authentication to reduce risk of credential compromise. 5. Conduct regular audits of user permissions and collection ownership to detect anomalies. 6. If immediate patching is not possible, deploy web application firewalls (WAF) rules to block unauthorized DELETE requests targeting collection endpoints. 7. Educate users about the importance of safeguarding credentials and recognizing suspicious activity. 8. Coordinate with RomM support or vendor for any additional security advisories or hotfixes. 9. Consider isolating RomM instances in segmented network zones to limit lateral movement in case of compromise.

Description

RomM (ROM Manager) allows users to scan, enrich, browse and play their game collections with a clean and responsive interface. Prior to 4.4.1 and 4.4.1-beta.2, an Authenticated User can delete collections belonging to other users by directly sending a DELETE request to the collection endpoint. No ownership verification is performed before deleting collections. This vulnerability is fixed in 4.4.1 and 4.4.1-beta.2.

References

Community reviews

Loading reviews…