Authenticated browser script execution via stored input
Published Jul 29, 2024 · Updated Feb 23, 2026
Stored XSS in M-Files Hubshare before 5.0.6.0 allows remote authenticated users to execute arbitrary JavaScript in another user’s browser. M-Files has not published the affected input field, rendering path, or missing neutralization operation that causes attacker-controlled content to be stored and replayed. An authenticated account must first store the crafted content, and a different user must view the affected content for script execution in that user’s session.
Summary
What happened
Stored XSS in M-Files Hubshare before 5.0.6.0 allows remote authenticated users to execute arbitrary JavaScript in another user’s browser. M-Files has not published the affected input field, rendering path, or missing neutralization operation that causes attacker-controlled content to be stored and replayed. An authenticated account must first store the crafted content, and a different user must view the affected content for script execution in that user’s session.
The record
- CVE
- CVE-2024-6881
- Published
- Jul 29, 2024
- Updated
- Feb 23, 2026
- Vendor
- M-Files
- Product
- M-Files Hubshare
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2024CVE publishedPublication date reported by the CVE source.
- Feb 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.0.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo