Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister subscriber account on target WordPress site
-
DeliveryInject XSS payload into Media Library Assistant metadata field
-
ExploitPayload stored server-side in media library
-
ExecutionAdmin views affected media library page
-
PersistMalicious script executes in admin browser context
-
ImpactAttacker captures admin session cookie or performs privileged actions
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 the attacker to hold at minimum a subscriber-level authenticated account on the target WordPress site, as confirmed by the CVSS PR:L metric. A second condition is that a higher-privileged user - most likely an administrator - must view the media library page or item containing the injected payload (UI:R per CVSS). Sites with open user registration are at materially higher risk because an attacker can self-register without social engineering. Exploitation is constrained by: the need for an active account on the target site, the requirement that an admin or editor view the poisoned content, and the absence of any impact if no privileged user browses the affected media library area. The A:L availability metric in the provided CVSS vector is not consistent with typical XSS impact and may reflect a scoring artifact rather than a confirmed availability consequence. |
| Impact | The CVSS 6.5 (Medium) score reflects the requirement for a low-privileged subscriber account (PR:L) and victim interaction (UI:R), which constrain exploitability compared to unauthenticated, no-interaction flaws. The network attack vector (AV:N) and low complexity (AC:L) indicate no special positioning or advanced technique is needed once an account is obtained. The scope change (S:C) elevates real-world impact - a subscriber could escalate effective access to administrator level by stealing session tokens. No EPSS data was supplied, no CISA KEV listing exists, and no POC code has been identified, all of which reduce immediate urgency. One anomaly to flag: the A:L availability metric in the provided CVSS vector is atypical for XSS, which does not ordinarily disrupt service availability; this should be verified against the vendor advisory. Overall, this is a genuine medium-priority issue for sites permitting open subscriber registration, but a lower priority where registration is restricted. |
| Exploit ScenarioDerived | An attacker registers a subscriber account on a WordPress site running Media Library Assistant 3.39 or earlier, then injects a JavaScript payload into a media file metadata field processed by the plugin. When a site administrator navigates to the media library and views the affected item or page, the payload executes silently in the admin's browser, exfiltrating the session cookie to an attacker-controlled endpoint and granting full administrative access to the WordPress installation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 20, 2026
Cross-site scripting in the Media Library Assistant WordPress plugin (versions up to and including 3.39) allows a subscriber-level authenticated user to inject malicious scripts into the media library that execute in the browser session of a higher-privileged user, such as an administrator, who subsequently views the affected content. The scope change indicated by the CVSS vector (S:C) means successful exploitation crosses from the plugin context into the victim's browser, enabling session hijacking or privilege escalation within the WordPress installation. No public exploit code or active exploitation has been identified at time of analysis.
RemediationAI
Update the Media Library Assistant plugin to the version released after 3.39 as confirmed by the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/media-library-assistant/vulnerability/wordpress-media-library-assistant-plugin-3-39-cross-site-scripting-xss-vulnerability-2; the exact patched version number is not confirmed from available input data and must be verified there. If an immediate update is not possible, disable open subscriber-level registration on the WordPress site to eliminate the attacker's entry point - this is the most effective compensating control, though it will prevent new user sign-ups. Alternatively, restrict subscriber accounts from accessing or contributing to the media library through role capability adjustments; note this may break plugin functionality for sites relying on subscriber media uploads. A WAF rule targeting common XSS payloads in media library metadata fields can provide additional layered defense, though it risks blocking legitimate HTML in media descriptions.
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
CWE-79 (Improper Neutralization of Input During Web Page Generation) describes the root cause: user-supplied input processed by the Media Library Assistant plugin is not adequately sanitized or encoded before being rendered in HTML output. The affected product is identified by CPE cpe:2.3:a:david_lingren:media_library_assistant:*:*:*:*:*:*:*:* - a WordPress plugin by developer David Lingren designed to enhance media file organization and display within the WordPress admin media library. The subscriber-level trigger indicates the vulnerable input path is accessible to the lowest default WordPress user role, a common attack pattern in stored XSS where low-privileged users supply input that is later rendered in contexts viewed by administrators. The scope change (S:C in the CVSS vector) reflects that script execution occurs in the victim's browser environment rather than the server.
Know when Media Library Assistant 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:L/UI:R/S:C/C:L/I:L/A:L
Subscriber account required (PR:L), admin must view injected content (UI:R), scope changes to victim browser (S:C); availability impact removed as XSS does not disrupt service availability.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Cross Site Scripting (XSS) in Media LIbrary Assistant <= 3.39 versions.
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 Media Library Assistant
View allThe Media Library Assistant plugin for WordPress is vulnerable to Local File Inclusion and Remote Code Execution in vers
The Media Library Assistant plugin before 2.82 for Wordpress suffers from a Local File Inclusion vulnerability in mla_ga
SQL injection in the Media Library Assistant WordPress plugin before version 3.40 allows authenticated users with the Au
Stored cross-site scripting in the Media Library Assistant WordPress plugin before 3.44 lets an authenticated user with
In the media-library-assistant plugin before 2.82 for WordPress, Remote Code Execution can occur via the tax_query, meta
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in David Lingre
Arbitrary file upload in the Media Library Assistant WordPress plugin (versions 3.39 and earlier) lets an authenticated
The Media Library Assistant plugin for WordPress is vulnerable to SQL Injection via the plugin's shortcode(s) in all ver
The Media Library Assistant plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order’ parameter wit
The Media Library Assistant plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type valida
Blind SQL injection in Media Library Assistant through version 3.32 allows authenticated attackers to execute arbitrary
Blind SQL injection in the WordPress plugin Media Library Assistant through version 3.42 allows an authenticated low-pri
EUVD-2026-63342
GHSA-7x9c-fph8-mph2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB