dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-5714

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Enable Media Replace plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘location_dir’ parameter in all versions up to, and including, 4.1.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The Enable Media Replace WordPress plugin fails to properly sanitize and escape the 'location_dir' parameter, allowing authenticated users with Author-level permissions or higher to inject persistent malicious scripts. These scripts execute in the browsers of users who access media library pages or related admin pages where the unsanitized data is displayed.

MitigationUpdate the Enable Media Replace plugin to version 4.1.9 or later. If no update is available, consider removing or disabling the plugin until a patched version can be installed, and limit user permissions to lower privilege levels.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Enable Media Replace plugin is installed
    Check your WordPress plugins directory for the enable-media-reply folder, or look for the plugin in the WordPress admin under Plugins > Installed Plugins
    Affected if The Enable Media Replace plugin appears in your WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (usually enable-media-replace.php) and locate the Version header in the plugin comment block, or check the version in the plugin's readme.txt file
    Affected if The version number is lower than 4.1.9 (any version prior to the fix)
  3. Check database for stored location_dir values
    Query your WordPress database (wp_options table or related tables where plugin settings are stored) for entries containing the location_dir parameter and inspect any stored values for suspicious patterns like <script tags, javascript:, or encoded payloads
    Affected if Any location_dir entries contain unsanitized HTML/JavaScript that was not escaped or filtered
  4. Verify user permission levels in WordPress
    Review your WordPress user roles and ensure no users with Author-level or higher permissions have been added recently or behave suspiciously
    Affected if You have users with Author, Editor, or Administrator roles who have access to the Enable Media Replace plugin functionality

Your environment is affected if Enable Media Replace plugin version is installed and is lower than 4.1.9, or if you find unsanitized script content stored in location_dir-related database entries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Enable Media Replace plugin to version 4.1.9 or later. If no update is available, consider removing or disabling the plugin until a patched version can be installed, and limit user permissions to lower privilege levels.

Recommended fix High confidence

Enable Media Replace plugin version 4.1.9 or latest available version

  1. 1. Log in to WordPress admin dashboard with Author-level or higher access
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Enable Media Replace' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/enable-media-replace/ and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 4.1.9 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5714 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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