Skip to main content
VulnerabilityPublished Updated

CVE-2026-40350: leepeuker movary · Incorrect Authorization

Affects leepeuker movarySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 0.71.1 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.71.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade movary and leepeuker/movary to 0.71.1.

Affected software

ProductAffectedFixed in
leepeukermovaryAffected
  • <0.71.1
Fixed in
  • 0.71.1
GitHubleepeuker/movarypkg:github/leepeuker/movaryOther threatsAffected
  • <0.71.1
Fixed in
  • 0.71.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade movary to version 0.71.1 or later, where the authorization flaw is patched. No other mitigation is indicated or recommended since the fix is available in the official release.

Description

Movary is a self hosted web app to track and rate a user's watched movies. Prior to version 0.71.1, an ordinary authenticated user can access the user-management endpoints `/settings/users` and use them to enumerate all users and create a new administrator account. This happens because the route definitions do not enforce admin-only middleware, and the controller-level authorization check uses a broken boolean condition. As a result, any user with a valid web session cookie can reach functionality that should be restricted to administrators. Version 0.71.1 patches the issue.

References

Community reviews

Loading reviews…