CVE-2026-26984
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 · uneditedLORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. Prior to versions 26.0.5, 27.0.2, and 28.0.0, an authenticated user with sufficient privileges can exploit a path traversal vulnerability to upload a malicious file to an arbitrary location on the server. Once uploaded, the file can be used to achieve remote code execution (RCE). An attacker must be authenticated and have the appropriate permissions to exploit this issue. If the server is configured as read-only, remote code execution (RCE) is not possible; however, the malicious file upload may still be achievable. This problem is fixed in LORIS v26.0.5 and above, v27.0.2 and above, and v28.0.0 and above. As a workaround, LORIS administrators can disable the media module if it is not being used.
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 · high confidenceLORIS neuroimaging research platform versions prior to 26.0.5, 27.0.2, and 28.0.0 contain a path traversal vulnerability in the media module that allows authenticated users with sufficient privileges to upload files to arbitrary server locations, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 26.0.5>= 27.0.0, < 27.0.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify LORIS installation locationLocate the LORIS web directory - typically installed at /var/www/loris or similar. Check for the presence of the main LORIS directory structure including htdocs, php, and modules folders.Affected if LORIS is installed and accessible via web
-
Determine installed LORIS versionCheck the version file in the LORIS root directory, commonly named 'VERSION' or 'docs/version.md'. Alternatively, inspect composer.json for the 'version' field.Affected if Installed version is < 26.0.5 OR >= 27.0.0 AND < 27.0.2 OR >= 28.0.0 AND < 28.0.0 (empty range indicates all versions < 28.0.0 are affected)
-
Verify media module is presentNavigate to the modules directory and check for the existence of a 'media' subdirectory. Typical path: /loris_root/modules/media/Affected if The media module directory exists in the installation
-
Check if media module is enabledExamine the LORIS configuration file (config.xml or config.xml.database) for module settings. Look for the 'media' module entry in the 'modules' section to determine if it is set to 'true' or enabled.Affected if Media module is listed as enabled in the LORIS configuration
-
Confirm user access to media upload functionalityReview user permissions in the LORIS user management interface or database. Check if any user roles have 'media' upload or 'media' write permissions granted.Affected if Authenticated users with media upload privileges exist in the system
You are affected if LORIS version is below 26.0.5, between 27.0.0-27.0.2, or below 28.0.0 AND the media module is enabled and accessible to authenticated users.
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.
dbcve · scoped26.0.527.0.2
Upgrade LORIS to version 26.0.5+, 27.0.2+, or 28.0.0+; alternatively, disable the media module if unused.
LORIS v26.0.5, v27.0.2, or v28.0.0+ (depending on your current major version branch)
- 1. Identify the currently installed LORIS version by checking the application's version file or admin interface
- 2. Review the current server configuration to understand if the media module is enabled and in use
- 3. If the media module is not actively used by researchers, disable it as an immediate workaround via the LORIS configuration
- 4. For a permanent fix, upgrade to LORIS v26.0.5 (if currently on 26.x), v27.0.2 (if currently on 27.x), or v28.0.0+ (if currently on 28.x)
- 5. After upgrading, verify the media module functionality works correctly and the path traversal vulnerability is resolved
- 6. Test that authenticated users with media upload privileges can still upload files to legitimate locations only
- 7. Review server logs for any suspicious upload activity that may indicate exploitation attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26984 — 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-2026-26984 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