CVE-2026-94387: stored XSS in Chatter change log

CISO Take

Aureus ERP before 1.6.0 renders old and new values in its Chatter field-change log without escaping, so any low-privileged user who can edit a tracked text field can plant script that runs in the browser of anyone viewing that record, including administrators. This is a general-purpose ERP, not an AI/ML system, and it is not a tracked AI package (no package match, 0/100 risk score, no known dependents), so AI-specific blast radius is minimal. Exploitation likelihood is low-to-moderate: EPSS is 0.00321 (top 77th percentile), it is not in CISA KEV, no Nuclei template exists, SSVC says TRACK, but a public PoC does exist. Upgrade to Aureus ERP 1.6.0 (fix in PR #1465), and review Chatter history for suspicious markup if any AI/ML dashboards or data workflows are integrated with the instance.

Sources:NVDEPSSATLASVulnCheckGitHub (aureuserp)

What is the risk?

Medium risk (CVSS 5.4). Network-exploitable with low complexity, but it needs an authenticated low-privilege account and a victim viewing the record. Scope is changed because script runs in the victim's session context, with limited confidentiality and integrity impact. A public PoC exists but there is no evidence of active exploitation (not in KEV, EPSS 0.32%). The AI/ML relevance is tangential: it matters only if the ERP is used alongside ML pipelines or AI operations tooling.

How does the attack unfold?

Initial Access

Attacker authenticates with a low-privilege account that can edit tracked text fields.

AML.T0012

Payload Injection

Attacker enters malicious markup into a tracked field, which is stored unescaped in the Chatter change log.

AML.T0049

Execution

An administrator or other user opens the record's Chatter panel and the script runs in their browser session.

Impact

Script performs privileged actions or steals session-accessible data, compromising confidentiality and integrity of ERP records.

Initial Access

Attacker authenticates with a low-privilege account that can edit tracked text fields.

AML.T0012

Payload Injection

Attacker enters malicious markup into a tracked field, which is stored unescaped in the Chatter change log.

AML.T0049

Execution

An administrator or other user opens the record's Chatter panel and the script runs in their browser session.

Impact

Script performs privileged actions or steals session-accessible data, compromising confidentiality and integrity of ERP records.

How severe is it?

CVSS 3.1

5.4 / 10

EPSS

0.3%

chance of exploitation in 30 days

Higher than 25% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

Exploit Available

Exploitation: MEDIUM

Sophistication

Trivial

Exploitation Confidence

medium

○Public PoC indexed (trickest/cve)

Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

What is the attack surface?

AVNetwork

ACLow

PRLow

UIRequired

SChanged

CLow

ILow

ANone

What should I do?

1 step

1) Upgrade Aureus ERP to 1.6.0 or later (commit 57cf5cf, PR #1465). 2) Until patched, restrict edit rights on tracked text fields to trusted users. 3) Deploy a strict Content-Security-Policy that blocks inline scripts. 4) Set session cookies HttpOnly and SameSite. 5) Audit Chatter field-change history for old_value/new_value entries containing HTML or script tags such as <script>, onerror= or javascript:. 6) Monitor for unusual admin-session actions following views of edited records.

What does CISA's SSVC say?

DecisionTrack

Exploitationnone

AutomatableNo

Technical Impactpartial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Code ExecutionData LeakagePluginAML.T0012- Valid Accounts AML.T0049- Exploit Public-Facing Application

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.6.2.6-AI system operation and monitoring

NIST AI RMF

MANAGE 2.3-Responses to previously unknown risks and vulnerabilities are planned and documented

Frequently Asked Questions

What is CVE-2026-94387?

Aureus ERP before 1.6.0 renders old and new values in its Chatter field-change log without escaping, so any low-privileged user who can edit a tracked text field can plant script that runs in the browser of anyone viewing that record, including administrators. This is a general-purpose ERP, not an AI/ML system, and it is not a tracked AI package (no package match, 0/100 risk score, no known dependents), so AI-specific blast radius is minimal. Exploitation likelihood is low-to-moderate: EPSS is 0.00321 (top 77th percentile), it is not in CISA KEV, no Nuclei template exists, SSVC says TRACK, but a public PoC does exist. Upgrade to Aureus ERP 1.6.0 (fix in PR #1465), and review Chatter history for suspicious markup if any AI/ML dashboards or data workflows are integrated with the instance.

Is CVE-2026-94387 actively exploited?

Proof-of-concept exploit code is publicly available for CVE-2026-94387, increasing the risk of exploitation.

How to fix CVE-2026-94387?

1) Upgrade Aureus ERP to 1.6.0 or later (commit 57cf5cf, PR #1465). 2) Until patched, restrict edit rights on tracked text fields to trusted users. 3) Deploy a strict Content-Security-Policy that blocks inline scripts. 4) Set session cookies HttpOnly and SameSite. 5) Audit Chatter field-change history for old_value/new_value entries containing HTML or script tags such as <script>, onerror= or javascript:. 6) Monitor for unusual admin-session actions following views of edited records.

What systems are affected by CVE-2026-94387?

This vulnerability affects the following AI/ML architecture patterns: Web application dashboards, ERP-integrated data pipelines.

What is the CVSS score for CVE-2026-94387?

CVE-2026-94387 has a CVSS v3.1 base score of 5.4 (MEDIUM). The EPSS exploitation probability is 0.32%.

What is the AI security impact?

Affected AI Architectures

Web application dashboardsERP-integrated data pipelines

MITRE ATLAS Techniques

AML.T0012Valid Accounts

AML.T0049Exploit Public-Facing Application

Compliance Controls Affected

ISO 42001: A.6.2.6

NIST AI RMF: MANAGE 2.3

What are the technical details?

Original Advisory

Aureus ERP before 1.6.0 contains a stored cross-site scripting vulnerability in the Chatter field-change log where old_value and new_value entries are rendered without proper escaping. Any user permitted to edit tracked text fields can inject malicious markup that executes when other users, including administrators, view the record's Chatter panel.

Exploitation Scenario

An attacker with a low-privilege account edits a tracked text field (for example a record title or note) and enters a payload with an event-handler tag. The change is logged in Chatter and old_value/new_value are rendered unescaped. When an administrator opens that record, the script runs in their session and performs privileged actions such as creating accounts or changing settings, or exfiltrates data. Where the ERP feeds data into ML or analytics workflows, the attacker could also use the admin context to tamper with records.

Weaknesses (CWE)

CWE-79Improper Neutralization of Input During Web Page GenerationPrimary CWE-79Improper Neutralization of Input During Web Page Generation

CWE-79 — Improper Neutralization of Input During Web Page Generation: 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.

[Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
[Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca

Source: MITRE CWE corpus.