CVE-2026-22675 | OCS Inventory NG Server up to 2.12.3 HTTP Header /ocsinventory User-Agent cross site scripting

VDB-355690 · CVE-2026-22675 · GCVE-0-2026-22675 OCS INVENTORY NG SERVER UP TO 2.12.3 HTTP HEADER /OCSINVENTORY USER-AGENT CROSS SITE SCRIPTING HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.4 $0-$5k 0.80+ Summaryinfo A vulnerability was found in OCS Inventory NG Server up to 2.12.3. It has been declared as problematic. Impacted is an unknown function of the file /ocsinventory of the component HTTP Header Handler. Executing a manipulation of the argument User-Agent can lead to cross site scripting. This vulnerability is registered as CVE-2026-22675. It is possible to launch the attack remotely. No exploit is available. A patch should be applied to remediate this issue. Detailsinfo A vulnerability classified as problematic was found in OCS Inventory NG Server up to 2.12.3. This vulnerability affects some unknown processing of the file /ocsinventory of the component HTTP Header Handler. The manipulation of the argument User-Agent 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. CVE summarizes: OCS Inventory NG Server version 2.12.3 and prior contain a stored cross-site scripting vulnerability that allows unauthenticated attackers to execute arbitrary JavaScript by submitting malicious User-Agent HTTP headers to the /ocsinventory endpoint. Attackers can register rogue agents or craft requests with malicious User-Agent values that are stored without sanitation and rendered with insufficient encoding in the web console, leading to arbitrary JavaScript execution in the browsers of authenticated users viewing the statistics dashboard. The weakness was published by Alexandre Nesic. The advisory is available at github.com. This vulnerability was named CVE-2026-22675 since 01/08/2026. The exploitation appears to be easy. The attack can be initiated remotely. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project. Applying the patch 78faf2ca8b897141ba4d337d75692ab8e405bd4e is able to eliminate this problem. Productinfo Vendor OCS Inventory Name NG Server Version 2.12.0 2.12.1 2.12.2 2.12.3 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 4.4 VulDB Meta Temp Score: 4.4 VulDB Base Score: 3.5 VulDB Temp Score: 3.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 5.4 CNA Vector (VulnCheck): 🔒 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: Patch Status: 🔍 0-Day Time: 🔒 Patch: 78faf2ca8b897141ba4d337d75692ab8e405bd4e Timelineinfo 01/08/2026 CVE reserved 04/06/2026 +87 days Advisory disclosed 04/06/2026 +0 days VulDB entry created 04/06/2026 +0 days VulDB entry last update Sourcesinfo Advisory: github.com Researcher: Alexandre Nesic Status: Confirmed CVE: CVE-2026-22675 (🔒) GCVE (CVE): GCVE-0-2026-22675 GCVE (VulDB): GCVE-100-355690 Entryinfo Created: 04/06/2026 23:57 Changes: 04/06/2026 23:57 (79) Complete: 🔍 Cache ID: 99:7F8:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸