CVE-2026-125822 in File Upload Plugin
Summary
by MITRE • 11/15/2026
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Nickboss WordPress File Upload wp-file-upload allows Stored XSS.This issue affects WordPress File Upload: from n/a through 5.2.3.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/15/2026
The identified security flaw represents a classic instance of Improper Neutralization of Input During Web Page Generation, commonly known as Cross-Site Scripting or XSS. Specifically, this vulnerability manifests as a Stored XSS within the Nickboss WordPress File Upload plugin, designated by its slug wp-file-upload. The scope of impact covers all versions from the initial release up through version 5.2.3. Unlike reflected XSS attacks where malicious scripts are executed immediately upon user interaction with a crafted link, stored vulnerabilities persist on the target server. This means that once an attacker successfully injects malicious code into the application's data store, such as via file metadata or upload descriptions, the script is served to every subsequent visitor who views the affected content. This persistence significantly amplifies the potential damage and widens the attack surface beyond a single user session.
The technical root cause lies in the insufficient sanitization of input fields associated with file uploads. When users interact with the plugin's interface to upload files, specific parameters or metadata are processed by the backend without adequate validation against special characters that hold meaning in HTML and JavaScript contexts. The application fails to encode these inputs before rendering them back into the browser environment. Consequently, if an attacker embeds a script tag within a file name, description, or other accepted input field during the upload process, the web server stores this payload unchanged. When another user accesses the page displaying information about that uploaded file, their browser interprets the stored content as executable code rather than plain text data. This execution occurs in the context of the victim's session with the WordPress site, granting the attacker a high degree of control over the client-side environment.
From an operational perspective, this vulnerability poses severe risks to both end-users and website administrators. Because the malicious script executes within the user's browser while they are authenticated or interacting with the site, attackers can perform actions on behalf of the victim. This includes stealing session cookies, which could lead to account takeover if administrative privileges are involved. Attackers may also redirect users to phishing sites designed to harvest credentials for other services, manipulate page content to display deceptive messages, or keylog user inputs such as passwords and credit card numbers. In a WordPress environment where multiple roles exist, the compromise of an administrator's session could allow full control over the website, including the installation of further malware, defacement, or using the server as part of a botnet. The impact is not limited to data theft but extends to integrity violations and potential denial of service through resource exhaustion caused by malicious scripts.
This vulnerability aligns with CWE-79, which defines Improper Neutralization of Script-Related HTML Tags in Web Pages, and maps directly to the MITRE ATT&CK technique T1059.007 for Command and Scripting Interpreter via JavaScript. The attack vector typically involves Initial Access through a trusted user or administrator who uploads maliciously crafted files, followed by Execution as the script runs in the victim's browser. To mitigate this risk, immediate action is required to update the WordPress File Upload plugin to version 5.2.4 or later, where the input validation logic has been corrected. For organizations unable to patch immediately due to compatibility concerns, implementing a Web Application Firewall can provide temporary protection by filtering out known XSS payloads in HTTP requests and responses. Additionally, enforcing strict Content Security Policy headers that restrict script execution sources can reduce the impact of any successfully injected scripts. Regular security audits and code reviews focusing on input handling for file upload features are essential preventive measures to avoid similar vulnerabilities in custom or third-party WordPress extensions.