CVE Intelligence

Rommapp Romm vulnerabilities

🔔 Create alert RSS Version checker

Published CVEs affecting Rommapp Romm: 3 record(s), with affected versions and fixes.
cpe:2.3:a:romm.app:romm

CVE-2025-65097 Medium · 6.5 CWE-284 Dec 3, 2025
Insecure Direct Object Reference (IDOR) Allows Unauthorized Deletion of User Collections
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.
CVE-2025-65096 Medium · 4.3 CWE-284 Dec 3, 2025
RomM Insecure Direct Object Reference (IDOR) Allows Unauthorized Access to Private Collections
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, users can read private collections / smart collections belonging to other users by directly accessing their IDs via API. No ownership verification or checking if the collection is public/private before returning collection data. This vulnerability is fixed in 4.4.1 and 4.4.1-beta.2.
CVE-2025-65027 High · 7.6 Public exploit CWE-79 Dec 3, 2025
RomM Chained XSS and CSRF Vulnerabilities Enable Admin Account Takeover
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.