Orchard CMS 1.10.3 through 1.11 Improper Authorization via Media Library Folder Permission Check
Affects Orchard 1.10.3 through 1.11 for accounts holding only ManageOwnMedia, the default for Author and Contributor roles. No fixed version is listed.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Orchard CMS, a content management system for building websites, is affected by this vulnerability. An authenticated user with the Author or Contributor role could view, copy, or delete other users' media files and delete media folders they should not have access to.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Orchard CMS 1.10.3 through 1.11 contains an improper authorization vulnerability in MediaLibraryService.CheckMediaFolderPermission() that allows authenticated Authors and Contributors to access other users' media. Attackers can display, clone, and delete other users' media items by content id and delete arbitrary media folders via FolderController.Delete().
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- OrchardCMS Orchard
From 1.10.3 · through 1.11
References 6
GitHub · OrchardCMS/Orchard
Questions about CVE-2026-119649
What does this mean?
An authenticated low-privilege user with only the ManageOwnMedia permission can read, delete, clone, and move other users' media items and delete other users' media folders on the same tenant. The flaw is not an anonymous bypass.Source: github.com
Am I affected, and how do I check?
The affected range is Orchard 1.10.3 through 1.11, with 1.11 as the tested version. The exposed setup is an account holding only ManageOwnMedia, which is the default for the built-in Author and Contributor roles. Check the installed Orchard version and the roles assigned to accounts.Source: github.com
What should I do about it?
The facts do not name a fixed version, so no upgrade target is confirmed. Do not assume a patched release exists until the vendor's advisory names one.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The facts list no workaround. Reviewing which accounts hold only ManageOwnMedia, such as Author and Contributor role members, shows where the exposure lies.Source: github.com