CVE-2026-69194

Deferred Deferred - Pending Action

Stored XSS in FileRise via Unsanitized Footer HTML

Publication date: 2026-10-14

Last updated on: 2026-10-15

Assigner: GitHub, Inc.

Description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.21.0, FileRise returns the stored branding.footerHtml value through the unauthenticated public site configuration API without server-side sanitization. The FileRise frontend already sanitizes this value before rendering it into the page, using an allowlist of simple footer tags and safe link handling. The unauthenticated public config API exposed raw admin-provided footer HTML to clients, which is still undesirable and could be unsafe for alternate clients or future render paths. An administrator must first store the malicious footer value. This issue is fixed in version 3.21.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-14

Last Modified

2026-10-15

Generated

2026-10-19

AI Q&A

2026-10-15

EPSS Evaluated

2026-10-18

NVD

CVE-2026-69194

Affected Vendors & Products

Vendor	Product	Version / Range
error311	FileRise	< 3.21.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-79	The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

Executive Summary

FileRise before version 3.21.0 has an issue where the unauthenticated public site configuration API returns the stored branding.footerHtml value without server-side sanitization. While the frontend sanitizes this value before rendering, the raw HTML is exposed to clients via the API, which could be unsafe for other clients or future changes.

Detection Guidance

Check FileRise version for anything below 3.21.0. Inspect the public site configuration API response for raw HTML in the branding.footerHtml field. Use curl to fetch the API endpoint and review the output for unsanitized content.

Impact Analysis

An attacker could store malicious HTML in the footer, which is then exposed via the unauthenticated API. This could lead to client-side attacks like XSS if alternate clients or future render paths do not sanitize the input properly.

Compliance Impact

This vulnerability exposes raw admin-provided footer HTML through an unauthenticated API, which could allow injection of malicious scripts or unauthorized content. This may violate data integrity and confidentiality principles in GDPR and HIPAA by enabling cross-site scripting (XSS) attacks or unauthorized data exposure if exploited.

Mitigation Strategies

Upgrade FileRise to version 3.21.0 or later. Review and remove any malicious footer HTML stored in the admin panel. Ensure future footer inputs are sanitized before saving.

Hi! I’m here to help you understand CVE-2026-69194. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70