CVE-2026-57722: Stored XSS in ShortPixel Enable Media Replace Plugin (CVSS 5.9)
ShortPixel's Enable Media Replace plugin contains a stored cross-site scripting (XSS) vulnerability that allows authenticated users with elevated privileges to inject malicious scripts into web pages. Unlike reflected XSS, stored XSS persists in the application, meaning the attack payload remains in the database and executes automatically whenever affected pages are viewed. This affects all versions through 4.2.1. An attacker would need administrative or editor-level access to inject the payload, but once stored, any user—including site visitors—viewing the compromised content could be affected.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.9 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-01 / 2026-07-02
NVD description (verbatim)
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in ShortPixel Enable Media Replace allows Stored XSS. This issue affects Enable Media Replace: from n/a through 4.2.1.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-57722 is a stored XSS vulnerability (CWE-79) in the Enable Media Replace plugin caused by improper input sanitization during web page generation. The vulnerability allows authenticated users with elevated privileges to inject JavaScript code that persists in the application's data store. When subsequent users access pages containing the malicious payload, the script executes in their browsers within the context of the vulnerable application. The CVSS 3.1 score of 5.9 (MEDIUM severity) reflects the requirement for high-privilege authentication and user interaction to trigger the vulnerability, though the impact reaches across session boundaries (noted by the 'S:C' scope change in the vector).
Business impact
A successful attack could compromise user sessions, steal sensitive data entered into the web application, redirect users to malicious sites, or deface site content. For WordPress installations relying on Enable Media Replace for media management, this risk extends to any site visitor viewing pages containing injected content. Depending on the site's purpose and data sensitivity, impacts could range from reputational damage and user trust erosion to compliance violations if personal or financial data is harvested. The persistent nature of stored XSS means the attack remains active until the malicious payload is explicitly removed.
Affected systems
Enable Media Replace plugin versions through 4.2.1 are affected. The vulnerability likely impacts WordPress installations, though the vendor/product field in source data is empty, so confirmation of the full deployment context is advisable. Organizations using this plugin for media asset management should audit their installations against the version threshold.
Exploitability
Exploitation requires authenticated access at an elevated privilege level (editor, admin, or equivalent). This requirement substantially raises the bar compared to unauthenticated XSS attacks. However, privilege escalation vulnerabilities in WordPress or other plugins, compromised user accounts, or insider threats could provide the entry point. Once injected, the payload executes automatically with no additional user interaction from victims—only the initial injection requires UI interaction from the attacker. The network-accessible nature (AV:N) means any authenticated user on the internet can attempt injection if they possess valid credentials.
Remediation
Update Enable Media Replace to the earliest patched version available above 4.2.1. Verify the patch version against the official ShortPixel or WordPress plugin repository advisory. Additionally, implement strict input validation and output encoding on any custom code that processes media metadata. Restrict plugin editor and upload capabilities to trusted administrators, and consider disabling media replace functionality if not actively needed.
Patch guidance
Check the official ShortPixel Enable Media Replace plugin page on the WordPress.org plugin directory or the vendor's website for a version release newer than 4.2.1. Apply updates through the WordPress admin dashboard or manually upload the patched version. Before deploying to production, test the update in a staging environment to ensure compatibility with your media workflow and other plugins. Verify that the patch release notes explicitly address CVE-2026-57722.
Detection guidance
Monitor for suspicious script injection attempts in WordPress admin activity logs, especially in media library operations and post/page edits. Use Web Application Firewall (WAF) rules to detect common XSS payloads in POST requests to the media replace endpoint. Review stored content (posts, pages, media metadata) for unexpected JavaScript or HTML tags using automated content scanning. Enable WordPress security logging plugins to capture admin user actions and privilege escalations. Look for unusual network requests originating from your site's frontend that might indicate script execution.
Why prioritize this
Although the CVSS score is MEDIUM (5.9) and the vulnerability requires authenticated high-privilege access, stored XSS has a broad blast radius once injected—it affects all site visitors without additional attack steps. The persistent nature means remediation cannot be delayed indefinitely. Prioritize this for organizations with multiple admin users, high-traffic sites, or user-generated content scenarios where account compromise is plausible. For single-admin, low-traffic sites, this can follow critical patches but should not be deferred beyond the next maintenance cycle.
Risk score, explained
The CVSS 3.1 score of 5.9 reflects: (1) Network-accessible attack vector, (2) Low attack complexity with no special conditions required, (3) High privilege requirement limiting attacker pool, (4) Required user interaction (the attacker must perform the injection), (5) Scope change because the impact crosses from the vulnerable component to other security contexts (site visitors), and (6) Low integrity impact (malicious content injection) with low confidentiality and availability impact. The privilege barrier prevents this from being high-severity, but the scope change and stored nature elevate it above the lowest tiers.
Frequently asked questions
Can someone without admin credentials exploit this?
No. The vulnerability requires authenticated access at an elevated privilege level (typically editor or admin role). However, if an attacker compromises or tricks an admin into performing the injection, the impact affects all subsequent site visitors, making account security critical.
How is stored XSS different from other XSS vulnerabilities?
Stored XSS persists in the application's database, so the malicious payload executes automatically whenever the affected page or content is viewed. Reflected XSS, by contrast, is delivered through a crafted URL and only affects the user who clicks the link. Stored XSS is generally considered more dangerous due to its persistent and widespread reach.
Will updating the plugin remove existing malicious payloads?
Updating the plugin patches the vulnerability to prevent new injections, but does not automatically clean stored malicious content from your database. After patching, audit your posts, pages, and media metadata for suspicious scripts and remove any found. Use security scanning tools or manual review to identify compromised content.
What if we cannot update immediately?
Implement compensating controls: restrict admin and editor access to only essential users, enable detailed audit logging of media operations, use a WAF to filter suspicious input, and regularly scan content for unexpected scripts. Set a firm update date and track progress. Do not delay patching indefinitely.
This analysis is based on vendor data and CVE record information current as of the published and modified dates. Patch version numbers and availability must be verified directly against official vendor advisories and the WordPress plugin repository. No exploit code or weaponized proof-of-concept is provided. Security teams should conduct their own risk assessment based on their environment, threat landscape, and business context. Always test patches in non-production environments before deployment. Source: NVD (public-domain), retrieved 2026-08-10. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2018-25384MEDIUMStored XSS in Wikidforum 2.20 Allows Authenticated Attackers to Inject Malicious Scripts
- CVE-2019-25731MEDIUMStored XSS in Zuz Music 2.1 Contact Form
- CVE-2019-25737MEDIUMStored XSS in Live Chat Unlimited 2.8.3 – Admin Session Compromise
- CVE-2019-25739MEDIUMGigToDo 1.3 Stored XSS Vulnerability in Proposal Descriptions
- CVE-2019-25742MEDIUMStored XSS in Zoner Real Estate WordPress Theme 4.1.1 – Admin Account Compromise Risk
- CVE-2019-25743MEDIUMWordPress Soliloquy Lite 2.5.6 Stored XSS Vulnerability
- CVE-2019-25744MEDIUMWordPress Popup Builder 3.49 Stored XSS Vulnerability – Exploit Prevention & Patch Guide