dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-13131

HIGH · 7.8 CVSS v3.1 Published 2025-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
A vulnerability was found in Sonarr 4.0.15.2940. The impacted element is an unknown function of the file C:\ProgramData\Sonarr\bin\Sonarr.Console.exe of the component Service. Performing manipulation results in incorrect default permissions. The attack is only possible with local access. The vendor confirms this vulnerability but classifies it as a "low severity issue due to the default service user being used as it would either require someone to intentionally change the service to a highly privileged account or an attacker would need an admin level account". It is planned to fix this issue in the next major release v5.

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 confidence

The Sonarr Windows service (Sonarr.Console.exe) is installed with incorrect default file permissions in the ProgramData directory, potentially allowing local users to modify the executable or configuration files. This permission misconfiguration could enable privilege escalation if the service is later changed to run under a higher-privileged account, or allow local tampering with service components.

MitigationUntil the v5 release, ensure the Sonarr service continues running under its default low-privilege service account and avoid changing it to highly privileged accounts (e.g., LocalSystem, domain admins). Verify file permissions on the Sonarr program directory restrict write access to administrators only.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Sonarr installation directory
    Check the ProgramData folder (typically C:\ProgramData\Sonarr) for the presence of Sonarr.Console.exe and config.xml. If Sonarr is installed elsewhere, identify the installation path.
    Affected if Sonarr is installed and the ProgramData directory exists on the system
  2. Identify the Sonarr service account
    Open Services, right-click the Sonarr service, go to Properties, and check the 'Log On' account. Alternatively, run: sc qc Sonarr
    Affected if The service is configured to run under a privileged account such as LocalSystem, or any account with administrative rights
  3. Inspect file permissions on Sonarr executables
    Right-click Sonarr.Console.exe in the installation directory, select Properties, then Security. Check which users or groups have Write or Modify permissions. Alternatively, use icacls Sonarr.Console.exe from an elevated command prompt.
    Affected if Users other than Administrators or SYSTEM have Write or Modify permissions to the executable
  4. Inspect file permissions on configuration files
    Right-click config.xml in the Sonarr ProgramData directory, select Properties, then Security. Check which users or groups have Write or Modify permissions. Alternatively, use icacls config.xml.
    Affected if Non-privileged users (such as standard users or the Users group) have Write or Modify permissions to config.xml or other configuration files
  5. Compare installed Sonarr version to fixed release
    Launch Sonarr and check the version displayed in the UI, or inspect the file properties of Sonarr.Console.exe. Determine if the version is prior to the v5 release which contains the permission fix.
    Affected if The installed version is before v5 and the file permissions allow write access for non-admin users

A user is affected if Sonarr is installed with versions prior to v5 and non-administrative users have write access to Sonarr executables or configuration files in the ProgramData directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until the v5 release, ensure the Sonarr service continues running under its default low-privilege service account and avoid changing it to highly privileged accounts (e.g., LocalSystem, domain admins). Verify file permissions on the Sonarr program directory restrict write access to administrators only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13131 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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