dbcve.org
LorisApplication · Mcgill

CVE-2026-33350

HIGH · 7.5 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 27.0.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. Prior to 27.0.3 and 28.0.1, a SQL injection has been identified in some code sections for the MRI feedback popup window of the imaging browser. Attackers can use SQL ingestion to access/alter data on the server. This vulnerability is fixed in 27.0.3 and 28.0.1.

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 confidence

A SQL injection vulnerability exists in the MRI feedback popup window of the imaging browser in LORIS prior to versions 27.0.3 and 28.0.1. Attackers can exploit unsanitized SQL input to access or modify data on the database server.

MitigationUpgrade LORIS to version 27.0.3 or 28.0.1 or later. If immediate patching is not possible, restrict access to the imaging browser module as a temporary mitigation.

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
LorisApplication
Affected:< 27.0.3= 28.0.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Identify LORIS installation and version
    Locate the LORIS installation directory and check the version file (typically in LORIS_ROOT / docs / Version or in the PHP configuration). Alternatively, access the LORIS login page and check any version information displayed, or inspect the composer.json or install manifest file in the web root.
    Affected if The installed version is lower than 27.0.3 or exactly 28.0.0
  2. Confirm MRI browser module is enabled
    Check the LORIS configuration file (config.xml or config.yml) for the 'ImagingBrowser' module setting. Verify that the imaging_browser module is set to 'true' or 'enabled'. The path is typically at LORIS_ROOT / project / config.xml or LORIS_ROOT / project / config.yml.
    Affected if The MRI browser module is enabled in the LORIS configuration
  3. Verify MRI feedback feature is accessible
    Attempt to access the MRI feedback popup functionality through the LORIS imaging browser interface. This typically involves navigating to imaging browser and selecting a scan that has feedback enabled. Check if the feedback_popup module or endpoint is accessible without authentication.
    Affected if The MRI feedback popup feature is accessible (no additional access controls blocking it)
  4. Check for suspicious database activity or logs
    Review LORIS Apache/nginx access logs and PHP error logs for unusual SQL syntax or injection patterns in requests to the imaging browser feedback endpoint. Look for SQL error messages that may indicate exploitation attempts.
    Affected if There are SQL injection attempts in logs or unexpected SQL errors related to the MRI feedback functionality

You are affected if LORIS version is less than 27.0.3 or exactly 28.0.0 AND the MRI browser module with feedback popup is enabled and accessible in your environment.

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.

dbcve · scoped
Upgrade available Upgrade to 27.0.3 or later
Fixed in 27.0.3
Interim mitigation

Upgrade LORIS to version 27.0.3 or 28.0.1 or later. If immediate patching is not possible, restrict access to the imaging browser module as a temporary mitigation.

Recommended fix High confidence

27.0.3 or 28.0.1 (depending on your current major version branch)

  1. Create a complete backup of the LORIS database and file system before upgrading
  2. Download LORIS version 27.0.3 or 28.0.1 from the official GitHub repository (github.com/aces/Loris)
  3. Review the release notes for the chosen version to understand any configuration or database changes
  4. Stop the LORIS web server and any background processing jobs
  5. Upgrade the PHP dependencies and Composer packages if required by the new version
  6. Run database migrations as specified in the release documentation
  7. Deploy the new LORIS code files to the server
  8. Start the web server and background jobs
Caveat Review release notes for potential database schema changes and backward compatibility considerations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Loris Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33350 — 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-2026-33350 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