CVE-2026-54198: Unauthenticated XSS in Media Library Assistant ≤3.35
Media Library Assistant versions 3.35 and earlier contain an unauthenticated cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts into the application without requiring a login. An attacker can craft a malicious link and trick a user into clicking it, causing the victim's browser to execute the injected code within the context of the Media Library Assistant application. This could lead to session hijacking, credential theft, or malware distribution.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.1 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-16 / 2026-06-17
NVD description (verbatim)
Unauthenticated Cross Site Scripting (XSS) in Media LIbrary Assistant <= 3.35 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-54198 is a reflected or stored XSS vulnerability (CWE-79) in Media Library Assistant up to version 3.35. The vulnerability exists because user-supplied input is not properly validated or encoded before being reflected in HTTP responses or stored in the application. The attack requires user interaction (UI:R) but requires no authentication (PR:N) and can affect confidentiality, integrity, and availability across security boundaries (S:C). The CVSS 3.1 vector indicates network accessibility with low attack complexity, making this a practical threat in real-world deployments.
Business impact
XSS vulnerabilities in web applications can undermine user trust and expose sensitive data. If Media Library Assistant is used to manage or distribute media content, compromised user sessions could allow attackers to modify, delete, or exfiltrate media assets. Depending on the application's role in your workflow, this could disrupt content management operations, lead to unauthorized modifications visible to end users, or result in credential compromise if users reuse passwords across systems.
Affected systems
Media Library Assistant versions 3.35 and earlier are affected. Organizations running this plugin or extension should immediately identify all installations and their version numbers. If your environment uses a newer version, confirm through the vendor advisory that the issue has been resolved.
Exploitability
This vulnerability is practical to exploit in real-world scenarios. No authentication is required, and exploitation depends only on a user clicking a malicious link or visiting a compromised page. The attack surface is significant if the application is accessible to internet users or if internal users can be socially engineered. The lack of CVSS KEV designation does not indicate the vulnerability is immaterial—it indicates it has not been confirmed in active exploitation campaigns at the time of this writing.
Remediation
Upgrade Media Library Assistant to a version later than 3.35 as soon as possible. Check the vendor's release notes or security advisory for the specific patched version and any configuration changes required. If an immediate upgrade is not feasible, implement input validation and output encoding controls, restrict access to the application via network segmentation, and monitor for suspicious XSS payloads in request logs.
Patch guidance
Contact the Media Library Assistant vendor or check their official release channels for the latest patched version. Verify the fix in release notes before deploying. Test the upgrade in a non-production environment first to ensure compatibility with your media management workflows. Plan for full deployment across all instances within your change management window.
Detection guidance
Monitor HTTP requests to Media Library Assistant for common XSS patterns, including script tags, event handlers (onload, onclick, onerror), and JavaScript protocol handlers in parameters. Use a web application firewall (WAF) to block payloads matching known XSS signatures. In logs, search for encoded variants of malicious input such as %3Cscript%3E, <script>, and similar obfuscations. Endpoint detection tools should flag unusual JavaScript execution originating from the Media Library Assistant domain.
Why prioritize this
Despite not appearing in the CISA KEV catalog, this HIGH severity vulnerability should be prioritized due to the combination of unauthenticated access, low attack complexity, and cross-boundary impact. Organizations with internet-facing or internally-shared Media Library Assistant instances face meaningful risk from opportunistic attackers. The requirement for user interaction does not significantly reduce risk in environments where social engineering is plausible.
Risk score, explained
The CVSS 3.1 score of 7.1 (HIGH) reflects a network-accessible vulnerability requiring no authentication, low attack complexity, and user interaction. The vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L indicates that successful exploitation affects confidentiality, integrity, and availability across security domains, justifying the elevated score. While availability impact may be limited in a typical XSS scenario, the cross-boundary scope (S:C) elevates the severity beyond a baseline reflected XSS.
Frequently asked questions
Do I need to be authenticated to exploit this vulnerability?
No. This vulnerability is unauthenticated, meaning an attacker does not need valid credentials to craft and deliver a malicious XSS payload. However, the victim (the user) must click a malicious link or visit a compromised page for the attack to succeed.
What is the difference between reflected and stored XSS in this context?
The CVE description does not explicitly distinguish between reflected and stored variants. Reflected XSS is delivered via a crafted URL and only affects the immediate victim. Stored XSS persists in the application and affects all users who view the compromised content. Your vendor advisory should clarify which type affects your deployment.
Is this vulnerability in the CISA Known Exploited Vulnerabilities (KEV) catalog?
As of the publication date, this vulnerability is not listed in the CISA KEV catalog. However, the absence of KEV status does not mean the vulnerability is not exploited in the wild or that it is low risk. KEV additions lag behind active exploitation campaigns.
What should I do if I cannot upgrade immediately?
Implement compensating controls: restrict network access to Media Library Assistant, deploy a WAF rule to block XSS payloads, educate users to avoid clicking untrusted links, and monitor logs for exploitation attempts. However, a temporary workaround is not a substitute for patching.
This analysis is based on publicly disclosed vulnerability information current as of the publication date. Vendor patch versions, upgrade timelines, and affected product details must be verified directly against the official vendor advisory. No exploit code or weaponized proof-of-concept details are provided. Organizations should conduct their own risk assessment based on their environment, user base, and media management dependencies. Source: NVD (public-domain), retrieved 2026-07-24. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20066HIGHWordPress CP Polls 1.0.8 Persistent XSS Vulnerability
- CVE-2016-20084HIGHWordPress Appointment-Booking-Calendar Unauthenticated XSS and Privilege Escalation
- CVE-2023-33999HIGHDOM-Based XSS in WP Mail Log Plugin – Analysis & Remediation
- CVE-2023-54351HIGHStored XSS in WordPress Sonaar Music Plugin 4.7 – Patch & Detection Guide
- CVE-2025-11262HIGHLink Whisper Free Stored XSS Vulnerability – Analysis & Patch Guidance
- CVE-2025-14773HIGHABB T-MAC Plus XSS Vulnerability – HIGH Risk Assessment
- CVE-2025-15654HIGHFox-themes Prague Reflected XSS Vulnerability – CVSS 7.1 (HIGH)
- CVE-2025-52759HIGHReflected XSS in UnboundStudio Accordion FAQ Plugin (Versions ≤2.2.1)