Skip to main content

Fortra FIM CVE-2026-12163

| EUVDEUVD-2026-38631 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-06-23 Fortra GHSA-r6vh-m36j-r62m
4.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to FIM as high-privilege user
  2. Delivery
    Navigate to node or database config field
  3. Exploit
    Store crafted XSS payload in Asset View UI
  4. Execution
    Victim user opens affected Asset View page
  5. Persist
    Browser renders payload as executable script
  6. Impact
    Exfiltrate victim session token or manipulate UI

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 of the stored XSS stage requires an authenticated Fortra FIM account with sufficient privileges to create or modify node or database configuration fields in the Asset View UI component - a high-privilege role as reflected by PR:H in the CVSS vector. The vulnerability does not affect default, unconfigured deployments where no privileged user has stored a malicious payload. For the payload to execute against a victim, a separate user must view the affected Asset View UI page in a web browser; this constitutes a second-stage condition beyond the initial storage step. Limiting factors include: (1) the PR:H requirement eliminates unauthenticated and low-privilege external attackers; (2) impact is bounded to confidentiality and integrity at Low severity - there is no availability impact on the FIM server itself; (3) only users who view the specific affected Asset View page are at risk of having the stored script execute against them.

Impact

The CVSS 3.1 base score of 5.5 (Medium) with vector AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N reflects a meaningful tension between access barrier and downstream impact. The PR:H requirement is a genuine gating factor: exploitation requires a user account with sufficient privileges to create or modify node or database configuration fields, which substantially limits the attacker population. However, the S:C (scope change) recognizes that a compromised privileged account can silently poison pages viewed by any other user of the Asset View UI, potentially including lower-privileged users. No EPSS score was provided in the input, and this CVE is not listed in the CISA KEV catalog, indicating no confirmed active exploitation. No public proof-of-concept has been identified. Real-world risk is best characterized as low-to-moderate: the PR:H bar means an external attacker would first need to compromise a high-privilege FIM account, making this primarily an insider-threat or post-compromise lateral movement vector rather than an opportunistic initial access path. The UI:N metric in the vendor-provided vector warrants scrutiny - see confidence notes.

Exploit ScenarioDerived

An insider threat or attacker who has already compromised a high-privilege Fortra FIM account navigates to a node or database configuration field in the Asset View UI and saves a crafted JavaScript payload - for example, a cookie-stealing script - as the field value. When a lower-privileged analyst or auditor subsequently opens the affected Asset View page during routine operations, the stored script executes silently in their browser session, exfiltrating their authentication token to an attacker-controlled endpoint. No public exploit code exists at time of analysis, but the attack primitive is well-understood and requires no specialized tooling beyond a browser.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 23, 2026

Stored cross-site scripting in Fortra File Integrity Monitoring (FIM) versions prior to 9.4.0.1 allows a highly privileged authenticated user to inject persistent script content into node or database configuration fields within the Asset View UI component. When another user subsequently views the affected Asset View page, the stored payload executes in their browser context rather than being safely escaped, enabling session hijacking, credential theft, or unauthorized UI manipulation against that victim. No public exploit code has been identified and this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog at time of analysis.

RemediationAI

The primary fix is to upgrade Fortra FIM to version 9.4.0.1 or later, as confirmed in the vendor advisory at https://www.fortra.com/security/advisories/product-security/fi-2026-009. If immediate upgrade is not feasible, restrict write access to node and database configuration fields within the Asset View UI to the smallest possible set of highly trusted accounts, thereby reducing the attacker population that could store malicious content. Additionally, enforce a Content Security Policy header on the FIM web interface if the product supports custom HTTP response headers, to limit the impact of any XSS payload execution. Audit existing configuration fields for unexpected script content as a detection measure. Note that restricting privileges as a compensating control does not eliminate the vulnerability for accounts that legitimately require configuration access.

Affected VersionsENISA

File Integrity Monitoring (FIM) 0 <9.4.0.1

Affected Packages

euvd file_integrity_monitoring_fim fix: 9.4.0.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-79 (Improper Neutralization of Input During Web Page Generation - Cross-site Scripting) describes a failure to sanitize or encode user-supplied data before it is rendered in a web page. In this case, Fortra FIM's Asset View UI component accepts text input for node or database configuration fields from privileged users but fails to HTML-encode or Content Security Policy-restrict that content at render time, so stored values are interpreted as executable HTML/JavaScript by the victim's browser rather than displayed as inert text. Fortra FIM is the rebranded successor to Tripwire Enterprise, a file integrity monitoring and security configuration management platform used in regulated enterprise environments. The affected CPE is cpe:2.3:a:fortra:fortra_file_integrity_monitoring_(fim):*:*:*:*:*:*:*:* for all versions prior to 9.4.0.1. The scope change (S:C in the CVSS vector) reflects the classic stored XSS dynamic: the attacker operates in one security boundary (the configuration editor) but the injected content executes in a different boundary (another user's authenticated browser session).

Know when Fortra File Integrity Monitoring Fim 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

Vendor (Fortra) PRIMARY MEDIUM
NVD 4.8 MEDIUM
AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
vuln.today AI 4.8 MEDIUM

PR:H reflects required high-privilege access to config fields; UI:R corrects the vendor vector since a victim must actively view the Asset View page for stored payload execution.

3.1 AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Fortra).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

2
CVSS changed
Jun 28, 2026 - 00:22 NVD
5.5 (MEDIUM) 4.8 (MEDIUM)
Patch available
Jun 24, 2026 - 02:00 EUVD

DescriptionNVD

Fortra File Integrity Monitoring (FIM), formerly Tripwire Enterprise, versions prior to 9.4.0.1 contain a stored cross-site scripting (XSS) vulnerability in the Asset View UI component. An authenticated user with sufficient privileges to create or modify affected node or database configuration fields could store script content that may be rendered as HTML instead of safely escaped text when the affected Asset View UI content is displayed.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
enterprise security niche product, formerly Tripwire Enterprise
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

24
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy