CVE-2026-35169
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. From to before 27.0.3 and 28.0.1, the help_editor module of LORIS did not properly sanitize some user supplied variables which could result in a reflected cross-site scripting attack if a user is tricked into following an invalid link. The same input vector could also allow an attacker to download arbitrary markdown files on an unpatched 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 · moderate confidenceThe help_editor module in LORIS does not properly sanitize user-supplied variables, leading to reflected cross-site scripting (XSS) when users are tricked into following a maliciously crafted link. The same insufficient input validation also allows attackers to download arbitrary markdown files from the server.
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>= 15.10, <= 27.0.2= 28.0.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed LORIS versionCheck the LORIS version by inspecting the version file (e.g., VERSION file in the LORIS root directory) or by accessing the LORIS login page footer which typically displays the version numberAffected if The installed version is >= 15.10 AND <= 27.0.2, OR exactly 28.0.0
-
Verify help_editor module is enabledCheck the LORIS configuration file (Config.xml or the modules configuration) to confirm whether the help_editor module is enabled for your installationAffected if The help_editor module is listed as enabled in the LORIS configuration
-
Check for XSS vulnerability in help_editorExamine the help_editor module source code (typically in htdocs/help_editor/ or similar path) for the parameter handling logic - look for lack of htmlspecialchars or similar sanitization on user-supplied parameters before outputAffected if The help_editor PHP code shows direct output of request parameters without proper escaping (e.g., no htmlspecialchars, ENT_QUOTES) on variables like $lang or $section
-
Check for path traversal vulnerabilityExamine the file download logic in the help_editor module - look for file path parameters that are not validated with realpath() or similar path sanitization before file operationsAffected if The help_editor file retrieval code accepts a parameter for file path and uses it directly in file operations without validating it stays within an allowed directory
You are affected if your LORIS version falls within 15.10 through 27.0.2 or is exactly 28.0.0 AND the help_editor module is enabled and contains the unsanitized input handling described in the vulnerability.
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 · scopedUpgrade LORIS to version 27.0.3 or 28.0.1 or later to receive the patch for the help_editor module's input sanitization issues.
LORIS 27.0.3 or 28.0.1
- Backup the current LORIS installation and database before proceeding
- Download LORIS version 27.0.3 or 28.0.1 from the official LORIS GitHub repository (github.com/aces/Loris)
- Extract the new version to your server
- Follow the standard LORIS upgrade procedure: update the codebase and run any required database migrations
- Clear any caches and verify the help_editor module functions correctly
- Confirm the XSS vulnerability is resolved by testing with the previously vulnerable input vectors
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-35169 — 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-35169 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