PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-6087 Novadigits technologies CVE debrief

A stored Cross-Site Scripting (XSS) vulnerability exists in the StockAgile API and management panel, specifically in the REST endpoint '/inventory/configuration/categories'. This allows for the injection and persistence of malicious JavaScript code through parameters such as 'code', 'name', and other text fields. The scripts entered are not filtered or validated correctly before being displayed on the web panel accessible to authenticated users.

Vendor
Novadigits technologies
Product
StockAgile
CVSS
MEDIUM 5.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-25
Original CVE updated
2026-09-25
Advisory published
2026-09-25
Advisory updated
2026-09-25

Who should care

Defenders responsible for the StockAgile API and management panel, as well as security teams and administrators of systems that use these components, should assess their exposure to this vulnerability and prioritize verification and mitigation efforts.

Why it matters

A stored Cross-Site Scripting (XSS) vulnerability in the StockAgile API and management panel requires verification and potential remediation to prevent the execution of malicious JavaScript code by authenticated users.

  • Authenticated users may be exposed to malicious JavaScript code
  • The vulnerability could allow for the execution of arbitrary JavaScript code
  • Defenders should verify the presence of this vulnerability in their inventory
  • Remediation efforts should focus on implementing input validation and filtering

Technical summary

The vulnerability exists in the REST endpoint '/inventory/configuration/categories' of the StockAgile API and management panel. It allows for the injection and persistence of malicious JavaScript code through parameters such as 'code', 'name', and other text fields. The scripts entered are not filtered or validated correctly before being displayed on the web panel accessible to authenticated users.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their inventory and assessing the exposure of authenticated users to the affected endpoint.

Recommended defensive actions

  • Verify the presence of the vulnerable endpoint in the inventory
  • Assess the exposure of authenticated users to the affected endpoint
  • Implement input validation and filtering for parameters such as 'code', 'name', and other text fields
  • Monitor for suspicious activity on the affected endpoint
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, additional information from the vendor and other sources may be necessary to fully understand the vulnerability's impact and to develop effective mitigations.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-6087 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-6087

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-6087 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-6087

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://www.incibe.es/en/incibe-cert/notices/aviso/stored-cross-site-scripting-stockagile-novadigits-technologies

    [email protected]

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.