Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister domain with target URL prefix
-
DeliveryInject payload into soundFile parameter via crafted cross-origin request
-
ExploitPayload stored in WordPress database
-
ExecutionLure authenticated admin to attacker-controlled page
-
PersistOrigin-prefix check bypassed, XSS executes in admin browser
-
ImpactExfiltrate session token or perform privileged admin action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires three concurrent conditions: (1) The attacker must control a domain whose full origin string is a leading prefix of the target WordPress site's backend URL - for example, controlling https://example.co while the target is https://example.com; this is an explicit non-default and non-trivial attacker precondition. (2) The victim must be an authenticated WordPress administrator with an active, logged-in session. (3) The victim must visit the attacker-controlled page while the File Manager admin screen is open in another browser tab or the same session context. The CVSS PR:N rating reflects that the attacker requires no account on the target site, which is accurate, but the domain-prefix requirement and the requirement for a privileged victim in a specific UI state substantially limit the realistic exploitation surface beyond what AC:L suggests. |
| Impact | The NVD-reported CVSS 3.1 score of 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) overstates practical exploitability. While the attacker requires no authentication on the target site (PR:N is accurate), the AC:L rating conflicts sharply with the description's explicit precondition: the attacker must control a domain whose origin string is a leading prefix of the target site's backend URL - a technically specific and non-trivial requirement. This single condition elevates real attack complexity well beyond AC:L. EPSS data was not provided; no KEV listing exists; no POC code is publicly confirmed. Taken together, the actual priority is lower than the CVSS score implies: exploitation is possible but requires meaningful attacker preparation and a narrowly defined victim state (admin with File Manager screen open). Defenders should treat this as a moderate-priority patch rather than a critical emergency. |
| Exploit ScenarioDerived | An attacker who has registered or controls a domain such as https://example.co (a prefix of the target https://example.com) crafts a page that injects a malicious value into the plugin's soundFile parameter. A WordPress administrator, logged in and with the File Manager admin screen active in a browser tab, visits the attacker's page; the origin-prefix relationship satisfies the plugin's cross-origin check, the stored XSS payload executes in the admin's browser, and the attacker can harvest session cookies, silently create rogue admin accounts, or perform authenticated API actions on behalf of the victim. No publicly confirmed POC code for this specific attack chain has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 16, 2026
Stored Cross-Site Scripting in the Advanced File Manager WordPress plugin (versions up to and including 5.4.12) allows unauthenticated network attackers to inject persistent malicious scripts via the unsanitized 'soundFile' parameter in elFinder.js. Successful exploitation grants script execution in an authenticated WordPress administrator's browser context, enabling session hijacking, credential theft, or administrative action abuse. No public exploit code or CISA KEV listing has been identified at time of analysis, and real-world impact is substantially constrained by a non-trivial domain-prefix precondition detailed below.
RemediationAI
Update the Advanced File Manager plugin to a version beyond 5.4.12 immediately; the upstream fix is referenced in WordPress plugin changeset 3645011 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3645011%40file-manager-advanced&new=3645011%40file-manager-advanced), though a specific patched version number has not been independently confirmed from available data - verify via the WordPress plugin repository or the Wordfence advisory. If upgrading is temporarily impossible, restrict access to the WordPress admin panel to trusted IP ranges via WAF or server-level rules, which removes the 'admin screen open' precondition from the attack chain; note this does not eliminate the stored payload if already injected. Additionally, implement a strict Content Security Policy (CSP) header on admin pages to limit inline script execution - be aware this may break other plugin functionality and requires testing. Review server logs for unexpected soundFile parameter values as an indicator of prior injection attempts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the elFinder file manager JavaScript library bundled within the plugin (elFinder.js, lines 4596, 4839, and 4856 per trac references). The 'soundFile' parameter - used to configure audio feedback for file operations - is written to the DOM without adequate sanitization or output encoding, satisfying CWE-79 (Improper Neutralization of Input During Web Page Generation). The affected CPE is cpe:2.3:a:saadiqbal:advanced_file_manager_-_ultimate_file_manager_for_wordpress_and_document_library_solution:*:*:*:*:*:*:*:*, covering all releases through 5.4.12. Because the injection persists in stored form, every subsequent page load by an eligible victim triggers the payload without further attacker interaction.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
AC:H reflects the mandatory domain-prefix precondition; all other metrics preserved from NVD vector as independently supportable.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Advanced File Manager - Ultimate File Manager for WordPress And Document Library Solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'soundFile' parameter in all versions up to, and including, 5.4.12 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the attacker to control a domain whose origin string is a leading prefix of the target site's backend URL (e.g. https://example.co against https://example.com), and the victim must be an authenticated WordPress administrator who visits the attacker-controlled page while the File Manager admin screen is open.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-59865
GHSA-r2jr-q8h6-hr93
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB