Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-6087 Overview
CVE-2026-6087 is a stored Cross-Site Scripting (XSS) vulnerability affecting the StockAgile API and management panel developed by Novadigits Technologies. The flaw resides in the server-side REST endpoint /inventory/configuration/categories, which accepts text parameters such as code and name without proper sanitization. An authenticated attacker can inject malicious JavaScript that persists in the backend and executes when any authenticated user loads the affected view in the management panel. The issue is categorized under CWE-79 (Improper Neutralization of Input During Web Page Generation).
Critical Impact
An authenticated remote attacker can execute arbitrary JavaScript in the browser context of other authenticated StockAgile users, enabling session abuse, data exfiltration, and panel actions on behalf of the victim.
Affected Products
- StockAgile (Novadigits Technologies) — API and management panel
- REST endpoint /inventory/configuration/categories
- Authenticated web console users of StockAgile
Discovery Timeline
- 2026-09-25 - CVE-2026-6087 published to NVD
- 2026-09-25 - Last updated in NVD database
- Advisory - Published by INCIBE CERT
Technical Details for CVE-2026-6087
Vulnerability Analysis
The vulnerability affects the inventory category configuration endpoint exposed under the StockAgile REST API. User-supplied values submitted to parameters such as code and name are stored in the backend without input validation or output encoding. When an authenticated operator opens the management panel view that renders these category records, the injected payload executes in the browser as part of the page DOM. Because the payload is persisted server-side, every subsequent page load that displays the tainted record triggers execution without further attacker interaction. The attack requires prior authentication but no elevated privileges, and the exploitation path is reachable over the network.
Root Cause
The root cause is missing input neutralization and improper output encoding on category configuration fields handled by /inventory/configuration/categories. The application trusts text inputs supplied through the REST API and renders them directly into the HTML context of the management panel, satisfying the preconditions for stored XSS described in CWE-79.
Attack Vector
An authenticated attacker submits a POST or PUT request to the vulnerable REST endpoint containing a JavaScript payload embedded in a text parameter such as code or name. The server persists the payload in the category record. When another authenticated user, including administrators, loads the categories view in the management panel, the browser interprets the stored payload and executes it under the panel's origin. The attacker can then access session tokens, invoke panel functions on behalf of the victim, or pivot to additional inventory records. See the INCIBE CERT Notice on XSS for the vendor-coordinated advisory. No public proof-of-concept exploit code has been released at the time of writing.
Detection Methods for CVE-2026-6087
Indicators of Compromise
- Category records in StockAgile containing HTML control characters (<, >, ", ') or substrings such as <script, onerror=, onload=, javascript: in code or name fields.
- HTTP requests to /inventory/configuration/categories with payload bodies that include encoded or raw JavaScript keywords.
- Unexpected outbound requests from authenticated user browsers immediately after loading the inventory categories view.
Detection Strategies
- Review StockAgile database tables that store inventory categories and query for suspicious characters in text fields.
- Deploy web application firewall rules that inspect request bodies to /inventory/configuration/categories for XSS signatures and encoded variants.
- Correlate authentication logs with category creation and modification events to identify low-privileged accounts planting persistent payloads.
Monitoring Recommendations
- Enable verbose access logging on the StockAgile API gateway and retain full request bodies for the vulnerable endpoint.
- Monitor browser Content Security Policy (CSP) violation reports from the management panel origin.
- Alert on anomalous session activity following category view loads, such as rapid API calls under administrative sessions.
How to Mitigate CVE-2026-6087
Immediate Actions Required
- Restrict access to the StockAgile management panel and REST API to trusted networks until a vendor-supplied patch is applied.
- Audit all records returned by /inventory/configuration/categories and remove entries containing script-like content.
- Rotate session tokens and credentials for any user who may have loaded tainted category records.
- Enforce least privilege on StockAgile accounts to limit which users can create or modify category entries.
Patch Information
No fixed version is listed in the NVD entry at the time of publication. Monitor the INCIBE CERT advisory and Novadigits Technologies communications for a security update addressing the stored XSS in the categories endpoint. Apply the patched release across all StockAgile instances once available.
Workarounds
- Place a reverse proxy or web application firewall in front of StockAgile and block requests to /inventory/configuration/categories containing HTML or JavaScript tokens.
- Deploy a strict Content Security Policy on the management panel that disallows inline scripts and restricts script sources to trusted origins.
- Temporarily disable category creation and editing for non-administrative roles pending remediation.
# Example NGINX rule to block obvious XSS payloads on the vulnerable endpoint
location /inventory/configuration/categories {
if ($request_body ~* "(<script|onerror=|onload=|javascript:)") {
return 403;
}
proxy_pass http://stockagile_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

