Skip to main content

Fabasoft Folio Client EUVDEUVD-2026-85790

| CVE-2026-97155 MEDIUM
Origin Validation Error (CWE-346)
2026-09-24 mitre GHSA-9hhv-69vm-5vcw
6.5
CVSS 3.1 · Vendor: mitre
View

Attack ChainAIDerived

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

  1. Access
    Lure user to malicious website
  2. Delivery
    Page sends web message to Folio Client
  3. Exploit
    Empty VALIDDOMAINS accepts untrusted origin
  4. Execution
    Invoke document download/open/sync functions
  5. Impact
    Manipulate or exfiltrate user's Folio documents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Origin validation
Exploitation Conditions

Exploitation requires that the victim's machine has Fabasoft Folio Client (a build before 26.0.0.10 / 26.4.0.76) AND the Fabasoft browser extension installed, with the registry value VALIDDOMAINS unset or empty - which is the default, meaning all web origins are trusted. The victim must actively browse to attacker-controlled or compromised web content (UI:R). Exploitation is LIMITED by: required user interaction (visiting a page), the need for both client and extension to be present and running, and the fact that setting VALIDDOMAINS to an allowlist of legitimate origins or upgrading to the fixed builds fully mitigates it; organizations that already restricted VALIDDOMAINS are not exposed.

Impact

This is a moderate, opportunistic-risk issue rather than an urgent priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N, 6.5) shows a network-reachable, low-complexity, unauthenticated flaw that nonetheless requires user interaction (UI:R) - the victim must visit an attacker-controlled web page while running both the Folio Client and its browser extension. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so all three exploitation-likelihood signals are absent; combined with a niche enterprise/government install base, this points to low probability of mass exploitation. The most notable data tension is that the vendor rated confidentiality C:N while the description explicitly lists 'downloading documents' and NVD tags it 'Information Disclosure' - because the client↔extension channel is web messaging (typically bidirectional), a malicious origin plausibly receives document data back, which would justify some confidentiality impact; verify with vendor. Conversely I:H seems generous: the invokable operations (download/open/sync) trigger legitimate client actions rather than arbitrary file modification, so real integrity impact is likely bounded. Net: a genuine origin-validation weakness worth patching on affected fleets, but not a drop-everything item absent evidence of exploitation.

Exploit ScenarioDerived

An attacker lures a user who has Fabasoft Folio Client and its browser extension installed to a malicious or compromised website. Because VALIDDOMAINS is empty by default, the page's JavaScript sends web messages that the client accepts from any origin, invoking privileged functions such as downloading, opening, or synchronizing the user's Folio documents. No public exploit code was identified at time of analysis, but the technique is straightforward web scripting requiring only that the victim visit the page.

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

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

Alert me

AnalysisAIv1 – Sep 24, 2026

Unauthenticated web origins can invoke local Fabasoft Folio Client functions on any Windows machine where both the Folio Client (builds before 26.0.0.10, or 26.x before the 26.4.0.76 April Release) and its companion browser extension are installed and the registry value VALIDDOMAINS is left unset - which is the shipped default, so every website is trusted. Because the client validates no calling origin, any page a user simply visits can trigger client operations such as downloading documents, opening documents, and synchronizing files, giving an attacker a drive-by means to influence document handling and file synchronization without any credentials (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N per the CVE record; our assessment scores it slightly lower at C:L/I:L/A:N given the functional scope observed). Exploitation requires the victim to browse attacker-controlled or compromised content, and there is no public exploit code identified at time of analysis - this is a moderate, opportunistic-risk issue rather than an urgent priority, and organizations that had already populated VALIDDOMAINS with an origin allowlist, or that upgrade to the fixed builds, are not exposed.

RemediationAI

The primary fix is to upgrade to a patched client build - vendor-released patch: Fabasoft Folio Client 2026 (Build 26.0.0.10) or Fabasoft Folio Client 2026 April Release (Build 26.4.0.76) - which enforces origin validation so that only trusted web origins can invoke client functions; see the vendor advisory at https://help.supportservices.fabasoft.com/index.php?topic=doc/Knowledge-Base/changes-to-fabasoft-folio-client-security-settings.htm. If immediate upgrading is not possible, apply the compensating control of populating the registry value VALIDDOMAINS with an explicit allowlist of the legitimate Fabasoft origins you actually use, rather than leaving it empty; this restores the intended origin restriction and is the same mechanism the fixed builds rely on, but the trade-off is that any legitimate portal or tenant origin omitted from the list will stop being able to trigger document download, open, and synchronization actions for users, so the list must be inventoried and tested carefully before rollout. Organizations that cannot do either can reduce exposure by removing the Fabasoft browser extension from endpoints that do not require it, or by uninstalling the Folio Client where it is not needed - accepting that this disables the document handling and file synchronization features for those users. Because exploitation depends on a user visiting malicious or compromised web content, web filtering and egress controls lower the likelihood of a successful trigger, but they are not a substitute for the allowlist or the upgrade. Note that no public exploit code has been identified at time of analysis, so prioritization can follow standard patch cycles for internet-exposed user endpoints rather than emergency response.

Affected VersionsENISA

Folio Client 0 <2026

Affected Packages

euvd folio_client fix: 2026

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

The Fabasoft Folio Client is a locally installed helper component on the user's workstation that communicates with the Fabasoft browser extension through browser web-messaging (extension-to-native-application messaging). The root cause is CWE-346, Origin Validation Error: the client never verified which web origin initiated a message, relying instead on an optional registry value, VALIDDOMAINS, to define the set of permitted origins. Because that value was optional and empty by default, the effective policy was 'trust all domains', so messages relayed from the extension to the local client - including requests to download, open, or synchronize files - were accepted regardless of the page the user was on. The relevant CPE, cpe:2.3:a:fabasoft:folio_client:*:*:*:*:*:*:*:*, identifies the client itself (all versions prior to the fixed builds) as the affected product; the extension is only the conduit, and the exposure exists because the client lacks an enforced origin allowlist at the trust boundary between web content and local native functionality. The client is distributed in customer environments including Fabasoft eGov-Suite deployments, which broadens the population of potentially affected endpoints beyond standalone installations.

Know when Folio Client 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 (mitre) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
vuln.today AI 5.4 MEDIUM

Remote page invokes client functions with no auth but needs the user to visit it (UI:R); bidirectional messaging can leak document data (C:L) and trigger file operations (I:L) rather than arbitrary modification; scope-change is arguable.

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

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

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

Lifecycle Timeline

1
Patch available
Sep 24, 2026 - 05:01 EUVD

DescriptionCVE.org

Fabasoft Folio Client before 2026, a locally installed component that communicates with the Fabasoft browser extension via web messaging, does not restrict which web origins may invoke its functions by default. The registry value VALIDDOMAINS, which limits permitted origins, was optional and empty by default, resulting in all domains being trusted. As a consequence, any website visited by a user with the Folio Client and browser extension installed could invoke client functions, e.g., related to downloading documents, opening documents, and synchronizing files. The first fixed builds are Fabasoft Folio Client 2026 (Build 26.0.0.10) and Fabasoft Folio Client 2026 April Release (Build 26.4.0.76). This client is, for example, shipped with Fabasoft eGov-Suite.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche enterprise ECM suite, mainly EU/DACH government and eGov deployments
Data Quality
4 sources
Confidence: Medium

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.1%
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· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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