LORIS has incorrect access checks in API for Imaging Browser
- 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
- Fix
- Fixed in 27.0.4, 28.0.2
- 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
Summary
LORIS, a self-hosted web application for managing neuroimaging research data and projects, is affected in its Imaging Browser API. An authenticated user can modify imaging data through this API even without the edit permission that the web interface requires, which could allow unauthorized changes to research data.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. In versions from 22.0.0 prior to 27.0.4 and from 28.0.0 prior to 28.0.2, the `API` for the `imaging_browser` module permits edits to imaging data without checking the frontend permissions that restrict editing in Imaging Browser. An authenticated `API` caller can therefore modify imaging data without the required edit authorization. Deployments that no longer use the `API` can disable it to remove access to this endpoint. This issue is fixed in versions 27.0.4 and 28.0.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- aces Loris
From 22.0.0 · fixed in 27.0.4; From 28.0.0 · fixed in 28.0.2