Vulnerability in Rommapp (CVE-2025-65097)
Summary
Vulnerability in Rommapp (CVE-2025-65097). Data can be tampered with by attackers. Mitigation: upgrade to 4.4.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-65097 has been found in Rommapp.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade Rommapp to 4.4.1 or later.
If unsure, ask your IT team or search "Rommapp CVE-2025-65097" on the vendor's site.
CVE-2025-65097 (Rommapp) — CWE-284 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.4.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in Rommapp.
Check the vendor advisory for the affected versions of Rommapp.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 4.4.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Rommapp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Rommapp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Rommappを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Rommapp to 4.4.1ステージング環境で 4.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。