What is the CVSS score of CVE-2026-15009?

CVE-2026-15009 has a CVSS 3.1 base score of 6.1 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.3%.

Advanced File Manager CVE-2026-15009

EUVD-2026-59865 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-08-16 Wordfence

GHSA-r2jr-q8h6-hr93

WordPress XSS Wordpress Plugin Advanced File Manager Ultimate File Manager For Wordpress And Document Library Solution Saadiqbal

6.1

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

6.1 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

vuln.today AI

4.7 MEDIUM

AC:H reflects the mandatory domain-prefix precondition; all other metrics preserved from NVD vector as independently supportable.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

4.0 AV:N/AC:H/AT:P/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Aug 16, 2026 - 05:10 vuln.today

CVE Published

Aug 16, 2026 - 04:24 cve.org

MEDIUM 6.1

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.

AnalysisAI

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.

Technical ContextAI

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.

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.