Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:LSummary
CVE-2026-30934 is a high-severity Cross-site Scripting (CWE-79) vulnerability in Filebrowser Filebrowser. Its CVSS base score is 8.9 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
FileBrowser Quantum, a free self-hosted web-based file manager, is affected by CVE-2026-30934, a stored cross-site scripting (XSS) vulnerability rated at CVSS 8.9 (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L) and mapped to CWE-79. The issue exists in versions prior to 1.3.1-beta and 1.2.2-stable, where share metadata fields such as title and description can be abused to inject malicious scripts. These fields are rendered into HTML on public share pages (/public/share/<hash>) without context-aware escaping, as the server employs Go's text/template package rather than the safer html/template, enabling script execution in victims' browsers.
An authenticated user with low privileges (PR:L) can exploit this vulnerability over the network (AV:N) with low complexity by crafting share metadata containing a JavaScript payload. Exploitation requires user interaction (UI:R), specifically a victim visiting the public share URL, after which the payload executes with changed scope (S:C). Successful attacks can result in high confidentiality and integrity impacts, such as session hijacking or data exfiltration, alongside low availability disruption.
The GitHub security advisory (GHSA-r633-fcgp-m532) and release notes for v1.2.2-stable and v1.3.1-beta confirm the vulnerability has been fixed by switching to proper HTML template escaping. Security practitioners should upgrade to these versions immediately, review existing shares for malicious metadata, and audit custom templates for similar text/template misuse.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10545
Vulnerability Data
FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to 1.3.1-beta and 1.2.2-stable, Stored XSS is possible via share metadata fields (e.g., title, description) that are rendered into HTML for /public/share/<hash> without context-aware escaping. The server uses text/template instead…
more
of html/template, allowing injected scripts to execute when victims visit the share URL. This vulnerability is fixed in 1.3.1-beta and 1.2.2-stable.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.3.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.
Input validation directly enforces neutralization of untrusted data before it reaches web output generation.
Output filtering can catch or sanitize unneutralized script content before it is served to users.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.
Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.
Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.
Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.
Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.
Webpage malware scanning and block-listing of known malicious sites reduce the likelihood that reflected or stored script payloads reach a user’s browser.