CVE-2025-14632

Filr – Secure document library <= 1.2.11 - Authenticated (Administrator+) Stored Cross-Site Scripting via HTML Upload

2026-01-16 14:11
Phap Nguyen Anh

Strategic Overview

Status
Patched in 1.2.12
Affected Version
<= 1.2.11
CVSS
4.4Medium
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2025-14632
View all Filr – Secure document library vulnerabilities

At a glance

CVE-2025-14632 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Filr WordPress plugin, affecting versions <= 1.2.11. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 1.2.12; sites on affected versions should update now. Disclosed January 2026, reported by Phap Nguyen Anh.

Vulnerability Overview

The Filr – Secure document library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via unrestricted file upload in all versions up to, and including, 1.2.11 due to insufficient file type restrictions in the FILR_Uploader class. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload malicious HTML files containing JavaScript that will execute whenever a user accesses the uploaded file, granted they have permission to create or edit posts with the 'filr' post type.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

CWE-434: Unrestricted Upload of File with Dangerous Type

Filr <= 1.2.11 carries this weakness at filr, and reaching it takes an account at Administrator level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Filr the fix is 1.2.12: builds <= 1.2.11 are affected, anything from 1.2.12 onward is not.

Remediation

Update to version 1.2.12, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Filr 1.2.12 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C