CVE-2025-13130
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 · uneditedA vulnerability has been found in Radarr 5.28.0.10274. The affected element is an unknown function of the file C:\ProgramData\Radarr\bin\Radarr.Console.exe of the component Service. Such manipulation leads to incorrect default permissions. The attack can only be performed from a local environment. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceRadarr 5.28.0.10274 has incorrect default file permissions on the service executable (Radarr.Console.exe), allowing local users unauthorized access to modify or replace the binary, potentially leading to privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Check Radarr versionOpen Windows PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Radarr*'} | Select-Object DisplayName, DisplayVersion. Alternatively, check the version shown in the Radarr UI under System > Info.Affected if The installed version is 5.28.0.10274
-
Locate Radarr.Console.exeOpen PowerShell and run: Get-ChildItem -Path 'C:\Program Files' -Recurse -Filter 'Radarr.Console.exe' -ErrorAction SilentlyContinue | Select-Object FullName. Typical path is C:\Program Files\Radarr\Radarr.Console.exe.Affected if The file exists at the found location
-
Check file permissions on Radarr.Console.exeRight-click Radarr.Console.exe in File Explorer, go to Properties > Security tab. Or run in PowerShell: Get-Acl 'C:\Program Files\Radarr\Radarr.Console.exe' | Select-Object -ExpandProperty Access | Where-Object {$_.FileSystemRights -match 'Write|Modify|FullControl' -and $_.AccessControlType -eq 'Allow' -and $_.IdentityReference -notmatch 'BUILTIN\Administrators|NT AUTHORITY\SYSTEM'Affected if Non-administrator users or groups (such as Users, Everyone, or authenticated users) have Write, Modify, or FullControl permissions on the executable
-
Verify service runs under a privileged accountOpen Services (services.msc), find the Radarr service, right-click and select Properties. Check the 'Log On As' account. It should be a specific service account or SYSTEM, not a standard user account.Affected if The service runs under a standard user account rather than SYSTEM or a dedicated service account
-
Confirm executable is replaceable by standard usersAs a non-administrative test (or via PowerShell with a test account), attempt to delete or rename the Radarr.Console.exe file. Or check inheritance: icacls 'C:\Program Files\Radarr\Radarr.Console.exe'Affected if Standard users can modify, delete, or replace the Radarr.Console.exe file
You are affected if Radarr version 5.28.0.10274 is installed AND standard (non-admin) users have Write, Modify, or FullControl permissions on the Radarr.Console.exe file, allowing them to replace the binary and escalate privileges.
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.
From vendor dataConfigure proper Windows ACLs on the Radarr service executable to restrict modification access to Administrators and SYSTEM only, then verify the service functions correctly.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13130 — 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-13130 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