dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9292

HIGH · 8.4 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Stored Cross-Site Scripting security issue exists within FactoryTalk® DataMosaix™ Private Cloud. The vulnerability stems from improper neutralization of user-supplied input within the Workflows configuration. An authenticated attacker with high privileges can inject malicious scripts that are permanently stored on the server. This vulnerability can result in the execution of malicious JavaScript when other users access the affected page, potentially allowing for account takeover, credential theft, or redirection to a malicious website.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in FactoryTalk DataMosaix Private Cloud's Workflows configuration module. An authenticated attacker with high privileges can inject malicious JavaScript through user-supplied input that gets permanently stored on the server, executing in the browsers of other users who access the affected page.

MitigationImplement strict input validation and proper output encoding for all user-supplied data in the Workflows configuration module to prevent script injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FactoryTalk DataMosaix Private Cloud installation
    Locate the installation directory or check system services for FactoryTalk DataMosaix components. On Windows, look in Program Files or check installed programs list.
    Affected if FactoryTalk DataMosaix Private Cloud is not installed on the system
  2. Verify Workflows configuration module is accessible
    Check if the Workflows module is enabled in the application. This can be done by reviewing the application's module configuration file or accessing the web interface to confirm the Workflows section is present and functional.
    Affected if The Workflows configuration module is enabled and accessible in the application
  3. Identify installed version of DataMosaix
    Check the application's About page, version information in the installation directory, or query the software version via the administrative interface or installed packages list.
    Affected if The installed version falls within any affected version range (compare against official vulnerability disclosure)
  4. Confirm high-privilege authenticated access exists
    Review user accounts and their privilege levels in the application. Check if any user accounts have high/privileged access to the Workflows configuration module.
    Affected if High-privilege authenticated users exist who can access the Workflows configuration functionality
  5. Inspect Workflows configuration input fields
    If you have access, navigate to the Workflows configuration module and examine the input fields where user-supplied data is accepted. Check if the application performs any output encoding on stored values.
    Affected if The Workflows module accepts user input without proper sanitization or encoding

A user is affected if FactoryTalk DataMosaix Private Cloud with the Workflows configuration module is installed, the installed version is within the affected range, and high-privilege users can access unvalidated input fields in the Workflows module.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and proper output encoding for all user-supplied data in the Workflows configuration module to prevent script injection.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9292 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data