Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain administrative access to KRIS
-
DeliveryInject script into template name field
-
ExploitPayload stored in Workflow Template
-
ExecutionVictim loads main dashboard
-
ImpactScript executes in victim's browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the attacker already possess administrative access to SQLView KRIS and use the Workflow Template feature to store a malicious payload in the 'template name' field, which the application renders without server-side sanitisation into an onclick attribute on the main dashboard. Execution additionally requires victim user interaction - a separate user must load the main dashboard and trigger the affected element - consistent with UI:R. The principal limiting factors are therefore the administrative privilege prerequisite (PR:H), which confines the attack to malicious or compromised admins, and the dependency on victim interaction with the dashboard; it is not a remote-unauthenticated issue. |
| Impact | This is a stored cross-site scripting (XSS) / code-injection flaw in SQLView KRIS's Workflow Template feature, rated CVSS 6.8 (Medium) in the input. The provided vector CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H is internally tense: PR:H and UI:R are consistent with the description (an attacker must already hold administrative access to store the payload, and a victim must subsequently load the dashboard), but the C:H/I:H/A:H impact rating is unusually high for a browser-executed stored XSS and appears inflated - XSS typically yields limited confidentiality/integrity impact in the victim's session rather than full system compromise. No EPSS score, CISA KEV listing, SSVC decision data, or proof-of-concept is present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The dominant mitigating signal is PR:H: the attacker must already be an administrator, which both narrows the realistic threat to insider/compromised-admin scenarios and substantially lowers real-world urgency. Net assessment: a legitimate but lower-priority medium-severity issue - the high base impact metrics overstate real risk given the admin precondition and absence of any exploitation signal. Verify the true impact scope and affected versions with the CSA advisory / SQLView vendor, as CWE is marked N/A and no version data is provided. |
| Exploit ScenarioDerived | An attacker who already holds administrative access to SQLView KRIS creates or edits a Workflow Template and embeds a malicious script into the 'template name' field; because the value is rendered unsanitised inside an onclick attribute on the main dashboard, the payload is stored. When another user (e.g., another administrator or operator) later loads the dashboard and interacts with the affected element, the script executes in their browser, enabling session/credential theft or actions in their authenticated context. No public proof-of-concept is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Stored cross-site scripting (XSS) in the Workflow Template feature of SQLView KRIS lets an actor who already holds administrative access store a script payload in the 'template name' field, which the application renders into an onclick attribute on the main dashboard without server-side sanitisation; the script then executes in the browser of any user who loads that dashboard and triggers the affected element. Per the CVSS vector (AV:N/AC:L/PR:H/UI:R), exploitation requires high administrative privileges and a separate victim's interaction, so the practical exposure is confined to malicious or compromised administrators rather than unauthenticated outsiders, and the independent assessment rates the resulting confidentiality and integrity impact as Low with no availability impact (CVSS 6.8, Medium). There is no KEV entry and no public exploit code identified at time of analysis.
RemediationAI
No vendor-released patch was identified in the available input data; the only reference is the CSA Singapore alert AL-2026-136 (https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-136/), which should be checked for a vendor fix and version guidance before assuming none exists. Until a patch is confirmed, apply contextual output encoding or HTML-attribute encoding to the 'template name' value wherever it is written into the dashboard's onclick attribute (or move the handler to a script block that reads data from a safely encoded JSON element) and add server-side input validation that rejects quotes, angle brackets, parentheses and event-handler syntax in template names; the trade-off is that legitimate template names containing punctuation may be refused or displayed differently, so validation rules should be agreed with application owners. Because exploitation requires administrative privileges, tighten and review the administrator role in SQLView KRIS: remove or disable the Workflow Template creation/editing permission for accounts that do not genuinely need it, audit existing template names for injected markup and purge any suspicious values, and rotate credentials or sessions for administrators who may have been compromised; the trade-off is reduced operational flexibility for teams that rely on delegated template authoring. As a containment measure, deploy a Content Security Policy that disallows inline script and inline event handlers on the dashboard, which neutralises attribute-injected payloads but will break any legitimate inline JavaScript the dashboard depends on and therefore requires testing. Finally, monitor administrative audit logs for unexpected template-name writes and treat dashboard-rendered content as untrusted output in any customisations.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a stored (persistent) cross-site scripting condition arising from missing output encoding of user-controlled data placed into an HTML event-handler attribute. The Workflow Template 'template name' value is persisted server-side and later interpolated into an onclick attribute on the main dashboard without server-side sanitisation or contextual escaping; because event-handler attributes are parsed as JavaScript, characters such as quotes and parentheses permit a stored value to break out of the attribute and execute script in the victim's session context. The input feed did not assign a CWE, though the pattern maps to the injection/improper-neutralization-of-input-during-web-page-generation class (commonly tracked as CWE-79), and the associated tag 'Code Injection' reflects the same root cause. The affected package is identified by CPE cpe:2.3:a:sqlview:sqlview_kris:*:*:*:*:*:*:*:*, i.e. the wildcard indicates the vendor product generally rather than a confirmed single fixed version boundary. The independent assessment applies a changed-scope vector (S:C) with Low confidentiality and integrity impact (C:L/I:L/A:N), meaning the injected script can read and alter data available to the victim's browser session but the available data does not support asserting full account takeover or high-severity impact.
Know when Sqlview Kris gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Stored XSS needs admin write access (PR:H) and victim dashboard interaction (UI:R); script runs in the victim's browser context (S:C) with limited C/I and no availability impact.
Primary rating from Vendor (CSA).
CVSS VectorVendor: CSA
DescriptionCVE.org
Unsanitised input in the "template name" field of SQLView KRIS's Workflow Template feature is rendered in "onclick" attributes on the main dashboard without proper server-side sanitisation, allowing an attacker with administrative access to inject and store malicious scripts that execute in the browsers of affected users.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-94804
GHSA-j7ff-q3f2-v94q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB