CVE-2026-57722
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStored XSS vulnerability in ShortPixel Enable Media Replace WordPress plugin allows malicious scripts to be injected and persisted in media metadata, executing when other users view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Enable Media Replace plugin is installedNavigate to WordPress Admin > Plugins, or check for the directory wp-content/plugins/enable-media-replace/ on the server file systemAffected if The plugin Enable Media Replace by ShortPixel is present in the WordPress installation
-
Check the installed plugin versionIn WordPress Admin > Plugins, click on the Enable Media Replace plugin to view its version number; alternatively, read the version from the main plugin file (usually enable-media-replace.php)Affected if The installed version falls within any vulnerable range (compare your version to the affected releases)
-
Identify media files that have been replacedCheck WordPress Media Library for files that were replaced using the Enable Media Replace feature; this feature modifies media metadata and is the injection pointAffected if Any media files were replaced using this plugin's functionality
-
Inspect media metadata for malicious scriptsQuery the WordPress database (wp_postmeta table) for meta_key values like '_wp_attachment_metadata' or '_media_replace_metadata' and examine the stored metadata for suspicious JavaScript tags, event handlers (onerror, onload, etc.), or encoded payloadsAffected if Media metadata contains unescaped HTML, script tags, or javascript: URIs that could execute when viewed
A user is affected if the Enable Media Replace plugin is installed and media replacement functionality has been used, with malicious scripts potentially present in media metadata that would execute when other users view that content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to the latest version of Enable Media Replace when available; sanitize and escape all media-related inputs and outputs until patch is applied.
- Consultation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57722 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data