CVE-2026-76178: Multiple vulnerabilities in Ocsreports for OCS Inventory NG
A stored Cross-Site Scripting (XSS) vulnerability in the notification template functionality of the endpoint /ocsreports/?function=notification. A user with administrator privileges can input malicious HTML content which is subsequently stored and displayed without proper sanitisation when other administrators access the template customisation view, allowing JavaScript code to be executed within the application’s security context and potentially compromising the sessions of other users with administrative privileges.
Security readout for executives and security teams
Plain-English summary
OCS Inventory NG Ocsreports 2.12.6 contains a stored cross-site scripting flaw in notification-template customisation. An existing administrator could save malicious HTML that runs when another administrator opens the affected view, potentially exposing privileged sessions or enabling actions within the application. The supplied sources do not establish broader version impact.
Executive priority
Treat affected 2.12.6 deployments as an urgent remediation item, especially where several administrators share access. The flaw does not provide unauthenticated entry, but it can turn one compromised or malicious administrator into broader privileged-session compromise. Require rapid inventory, access review, vendor-guided remediation, and investigation of suspicious template changes.
Technical view
CVE-2026-76178 is CWE-79 at /ocsreports/?function=notification. Stored notification-template content is displayed without proper sanitisation. Exploitation requires administrator privileges and interaction by another administrator. The CVSS 4.0 score is 9.2, reflecting potentially high confidentiality and integrity impact across security boundaries, with no stated availability impact.
Likely exposure
Exposure is supported for Ocsreports 2.12.6 where administrators can customise notification templates. Risk is greatest when multiple administrators use the application or privileged access is insufficiently controlled. The bundle marks other versions unaffected by default, but does not provide enough detail to independently confirm every release or deployment configuration.
Exploitation context
The attacker must already hold administrator privileges, store malicious content, and wait for another administrator to access the template customisation view. This limits initial access but creates a path to compromise additional privileged sessions. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The source bundle identifies the vulnerable endpoint, stored-XSS mechanism, administrator prerequisite, and victim interaction. It does not name a fixed version, patch, proof of concept, observed exploitation, or complete affected-version range. Validation should remain non-executing: inspect stored content and logs safely rather than attempting to trigger scripts.
Mitigation direction
Check INCIBE-CERT and OCS Inventory NG guidance for an approved fixed release or vendor mitigation.
Restrict Ocsreports administrator access to trusted, necessary personnel until remediation is confirmed.
Review notification templates and remove unexpected HTML or script-like content using approved administrative procedures.
Revoke affected administrative sessions and reset credentials if suspicious template activity or session compromise is identified.
Validation and detection
Inventory Ocsreports deployments and verify whether version 2.12.6 is present.
Confirm which accounts can modify notification templates and whether each still requires that privilege.
Inspect stored notification templates for unexpected HTML or script-like content without rendering it in a browser.
Review administrative and application logs for unexplained template changes or unusual privileged-session activity.
After remediation, confirm the installed version and applicable vendor advisory match.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.