CVE-2026-69194: FileRise: Unsanitized footerHtml in Public Site Config

Published Oct 14, 2026
·
Updated

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.

Affected Software

1 affected component
FileRise FileRise<3.21.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade FileRise to a version that resolves this vulnerability.

    Fixed in 3.21.0

Event History

Oct 14, 2026
CVE Published
via MITRE·08:32 PM
Data Sourced
via MITRE·08:32 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can retrieve the affected value?

Any unauthenticated client that can access the public site configuration API can receive the stored branding.footerHtml value. Exploitation requires an administrator to have first saved a malicious footer value.

2

Are standard FileRise frontend users directly exposed to script execution?

The FileRise frontend sanitizes footerHtml before rendering it, using an allowlist of simple footer tags and safe link handling. The remaining concern is exposure of the raw value to alternate clients or future rendering paths that do not apply equivalent sanitization.

3

Which versions are affected and what fixes the issue?

FileRise versions prior to 3.21.0 are affected. Upgrade to version 3.21.0, which fixes the unauthenticated API's return of unsanitized footer HTML.

4

What can be done before upgrading?

Review the configured branding.footerHtml and remove any untrusted or malicious HTML. Limit access to the public site configuration API where deployment controls allow it, since that endpoint exposes the raw stored value to unauthenticated clients.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203