Stored XSS via undisclosed input handling
Published Jan 22, 2026 · Updated Jan 22, 2026
Stored XSS in Infility Global 2.15.11 and earlier allows remote attackers to execute scripts in a victim's browser via stored input. Patchstack has not disclosed the affected field, request parameter, or code path that stores and later renders the unneutralized input. Exploitation requires a victim to view the stored content; the published assessment requires no attacker privileges and bounds impact to browser-context data access, modification, and interruption.
Summary
What happened
Stored XSS in Infility Global 2.15.11 and earlier allows remote attackers to execute scripts in a victim's browser via stored input. Patchstack has not disclosed the affected field, request parameter, or code path that stores and later renders the unneutralized input. Exploitation requires a victim to view the stored content; the published assessment requires no attacker privileges and bounds impact to browser-context data access, modification, and interruption.
The record
- CVE
- CVE-2025-68864
- Published
- Jan 22, 2026
- Updated
- Jan 22, 2026
- Vendor
- Infility
- Product
- Infility Global
- Classifications
- CWE-79, CAPEC-592, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2026CVE publishedPublication date reported by the CVE source.
- Jan 22, 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=n/a <=<= 2.14.50
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