CVE-2025-65097
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 · uneditedRomM (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.
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 confidenceRomM fails to verify collection ownership in the DELETE endpoint, allowing any authenticated user to delete any collection by directly targeting its ID. This is an Insecure Direct Object Reference (IDOR) authorization bypass vulnerability.
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< 4.4.1= 4.4.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify RomM installation and versionLocate the RomM application installation and determine the installed version by checking the version file, package metadata, or the application's about/API endpointAffected if The installed version is < 4.4.1 or equals 4.4.1 (the affected range)
-
Verify collection deletion endpoint existsConfirm the RomM API includes a DELETE endpoint for collections (typically /api/collections/{id} or similar path accepting collection IDsAffected if The DELETE endpoint for collections is present and accessible to authenticated users
-
Confirm multiple user accounts existCheck if more than one user account is registered in the RomM instanceAffected if Multiple authenticated users exist in the system, enabling the IDOR vulnerability to be exploited across user boundaries
-
Test collection ownership enforcementAs an authenticated user, attempt to access or construct a request to delete a collection belonging to a different user by directly targeting its ID in the DELETE endpointAffected if The system allows deletion of collections owned by other users without proper ownership verification
A user is affected if their RomM installation version falls within < 4.4.1 or = 4.4.1 AND the DELETE collections endpoint is accessible to authenticated users who can target collection IDs they do not own.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.4.1
Upgrade RomM to version 4.4.1 or 4.4.1-beta.2 which implements proper ownership verification before allowing collection deletion.
4.4.1 or 4.4.1-beta.2
- Backup your RomM database and configuration files before upgrading
- Update RomM to version 4.4.1 (or 4.4.1-beta.2) using your deployment method (e.g., Docker, package manager, or source)
- Restart the RomM service after upgrading
- Verify the upgrade was successful by checking the application version
- Log in as an authenticated user and confirm that users can only delete their own collections, not those belonging to other users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65097 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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