CVE-2026-35403 | aces Loris up to 27.0.2/28.0.0 Header survey_accounts Content-Type cross site scripting

VDB-356371 · CVE-2026-35403 · GCVE-0-2026-35403 ACES LORIS UP TO 27.0.2/28.0.0 HEADER SURVEY_ACCOUNTS CONTENT-TYPE CROSS SITE SCRIPTING HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.5 $0-$5k 0.88+ Summaryinfo A vulnerability, which was classified as problematic, has been found in aces Loris up to 27.0.2/28.0.0. This issue affects the function survey_accounts of the component Header Handler. This manipulation of the argument Content-Type causes cross site scripting. This vulnerability is handled as CVE-2026-35403. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component. Detailsinfo A vulnerability was found in aces Loris up to 27.0.2/28.0.0. It has been declared as problematic. Affected by this vulnerability is the function survey_accounts of the component Header Handler. The manipulation of the argument Content-Type with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is: LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. From 15.10 to before 27.0.3 and 28.0.1, there is a potential for a cross-site scripting attack in the survey_accounts module if a user provides an invalid visit label. While the data is properly JSON encoded, the Content-Type header is not set causing the web browser to interpret the payload as HTML, opening the possibility of a cross-site scripting if a user is tricked into following an invalid link. This vulnerability is fixed in 27.0.3 and 28.0.1. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-35403 since 04/02/2026. The exploitation appears to be difficult. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK. Upgrading to version 27.0.3 or 28.0.1 eliminates this vulnerability. Productinfo Vendor aces Name Loris Version 27.0.0 27.0.1 27.0.2 28.0 Website Product: https://github.com/aces/Loris/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 4.5 VulDB Meta Temp Score: 4.5 VulDB Base Score: 2.6 VulDB Temp Score: 2.5 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.5 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Cross site scripting CWE: CWE-79 / CWE-94 / CWE-74 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Loris 27.0.3/28.0.1 Timelineinfo 04/02/2026 CVE reserved 04/08/2026 +6 days Advisory disclosed 04/08/2026 +0 days VulDB entry created 04/08/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-35403 (🔒) GCVE (CVE): GCVE-0-2026-35403 GCVE (VulDB): GCVE-100-356371 Entryinfo Created: 04/08/2026 21:11 Changes: 04/08/2026 21:11 (66) Complete: 🔍 Cache ID: 99:AB0:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸