Skip to main content

Enable Media Replace CVE-2026-114422

| EUVDEUVD-2026-113743 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-10-30 contact@wpscan.com GHSA-57rw-qx68-p67c
7.5
CVSS 3.1 · Vendor: wpscan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Store malicious serialized object in media metadata (unauthenticated)
  2. Delivery
    Wait for privileged user to run replace-and-update-links
  3. Exploit
    Unsafe deserialization instantiates injected PHP object
  4. Execution
    Object injection triggers local file inclusion
  5. Persist
    Include attacker-influenced PHP/HTML file
  6. Impact
    Achieve remote code execution

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

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 plugin's 'replace media and update links' routine to be invoked by a user who holds upload access - the deserialization only occurs during that specific media-replacement workflow, so unauthenticated injection alone is inert until a privileged user acts (UI:R). Full escalation to RCE additionally requires that an attacker-influenced PHP or HTML file already be present on the server for the local file inclusion to execute; without such a file the impact is limited to object injection and LFI of existing files. Limiting factors: affected versions are specifically 4.1.4 through <4.2.3 (4.1.3 and earlier, and 4.2.3+, are not affected), the AC:H rating reflects the chained prerequisites, and no automated/scalable exploitation is possible (SSVC Automatable: no). The exact trigger beyond 'unrestricted class deserialization of stored metadata' is as described in the advisory.

Impact

Signals point to a serious-but-conditional issue rather than a drop-everything emergency. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.5 HIGH) describes a network-reachable flaw that an unauthenticated actor can seed (PR:N) but that only fires when a user with upload access performs a media replacement (UI:R) and that carries high attack complexity (AC:H), consistent with the chained prerequisites in the description. SSVC reinforces this: Technical Impact is 'total' (full object injection leading to LFI/RCE) but Exploitation is 'none' (no observed exploitation) and Automatable is 'no' - it cannot be sprayed at scale because a privileged human action is the trigger. EPSS of 0.82% (57th percentile) is low-to-moderate and aligns with the SSVC 'none'/'no' reading: no evidence of imminent mass exploitation. There is no CISA KEV listing, and no PoC is confirmed as working exploit code in the input (only a WPScan advisory reference). The one notable amplifier is that this is an explicit REGRESSION of CVE-2023-4643 (fixed in 4.1.3, reintroduced in 4.1.4) - a previously-patched, well-documented bug class, which lowers the research barrier for anyone who studies the prior advisory. Net: the vendor/aggregator priority of 'this_week' is a reasonable middle ground - patch promptly because impact is total and the gadget/technique is already public from the 2023 fix, but the UI:R + AC:H + Automatable:no combination makes widespread opportunistic exploitation unlikely.

Exploit ScenarioDerived

An unauthenticated attacker submits input that is stored as media metadata containing a serialized PHP object payload. Later, a legitimate user with upload access runs the plugin's replace-and-update-links routine, which deserializes the stored metadata without class restrictions, instantiating the attacker's object (PHP Object Injection) and triggering local file inclusion of an existing PHP/HTML file; where an attacker-influenced PHP or HTML file already exists on the server, this escalates to remote code execution. No confirmed working exploit code is identified in the input, though a WPScan advisory reference exists and the bug is a known regression.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 30, 2026

PHP object injection in the Enable Media Replace WordPress plugin (versions 4.1.4 through 4.2.3) lets unauthenticated users plant a serialized object in stored metadata that is deserialized when a user with upload access runs the plugin's replace-media-and-update-links routine, yielding object injection and local file inclusion of existing PHP/HTML files and potential escalation to remote code execution when an attacker-influenced PHP or HTML file is already present on the server. The flaw is a regression of CVE-2023-4643 (fixed in 4.1.3, reintroduced in 4.1.4); a vendor patch is available in 4.2.3. EPSS is 0.82% (57th percentile), SSVC records Exploitation: none and Automatable: no, and no public exploit has been identified at time of analysis.

RemediationAI

Vendor-released patch: upgrade the Enable Media Replace plugin to 4.2.3, which is the first version outside the reintroduced regression range; sites still on 4.1.3 or earlier already sit outside the affected window, but any installation on 4.1.4 through 4.2.2 should be updated. Confirm the deployed plugin version after updating, since the flaw was previously fixed and then regressed, and track the WPScan advisory at https://wpscan.com/vulnerability/e0fa983d-19b6-438b-96c1-7ae6e8ccace4/ for any further revision. Until the update is applied, note that the injection only becomes live when a user with upload access runs the media replace-and-update-links routine, and that escalation to code execution requires an attacker-influenced PHP or HTML file to already be resident on the server, so limiting who can perform media replacements and keeping executable file uploads out of the uploads directory reduce exposure while patching; these are partial measures, not substitutes for updating to 4.2.3.

Affected VersionsENISA

Enable Media Replace 4.1.4 <4.2.3

Affected Packages

euvd enable_media_replace fix: 4.2.3

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-502 (deserialization of untrusted data) in a WordPress plugin: the media replace-and-update-links workflow deserializes stored metadata without restricting the PHP classes that may be instantiated, so an attacker-supplied serialized payload becomes a live PHP object inside the WordPress process. The injected object is only materialized when a user holding upload access invokes that specific replacement routine, which is why the assessed vector carries UI:R and AC:H - the unauthenticated injection step is inert until the privileged workflow is triggered, and the availability of usable gadget chains determines how far the object injection travels. The secondary primitives are local file inclusion of PHP/HTML files already on the server and, where an attacker-influenced PHP or HTML file is present, escalation to remote code execution. The issue is a regression: the same deserialization flaw class was addressed as CVE-2023-4643 in 4.1.3 and reintroduced in 4.1.4, so the vulnerable window is precisely 4.1.4 through below 4.2.3.

Know when PHP 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

Vendor (wpscan) PRIMARY 7.5 HIGH
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.5 HIGH

Unauthenticated payload injection sets PR:N, but a privileged user must run the replace routine (UI:R) and RCE needs an attacker-influenced file present, justifying AC:H; successful object injection yields total C/I/A impact.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (wpscan).

CVSS VectorVendor: wpscan

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 30, 2026 - 14:37 NVD
7.5 (HIGH)
Patch available
Oct 30, 2026 - 07:16 EUVD
CVE Published
Oct 30, 2026 - 06:16 cve.org
HIGH 7.5
CVE Published
Oct 30, 2026 - 06:16 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Enable Media Replace WordPress plugin before 4.2.3 does not restrict the classes allowed when deserializing stored metadata during its media replace-and-update-links routine, allowing unauthenticated users to inject a PHP object that is instantiated when a user with upload access performs a routine media replacement, resulting in PHP Object Injection and local file inclusion of existing PHP/HTML files, which can be escalated to remote code execution where an attacker-influenced PHP or HTML file is present on the server. This is a regression of CVE-2023-4643, which was fixed in 4.1.3 and reintroduced in 4.1.4.

Executive ViewAI

Why It Matters

The Enable Media Replace WordPress plugin (versions 4.1.4-4.2.3) contains a high-severity vulnerability that allows unauthenticated users to inject malicious objects, potentially leading to local file inclusion and remote code execution. This affects any organization using the plugin on public-facing WordPress sites, and successful exploitation could enable an attacker to execute arbitrary code, compromising site integrity and data confidentiality. Leadership should prioritize patching because this is a regression of a previously fixed flaw, indicating persistent risk.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.8%
Top 43% exploitable
Prevalence
Medium
popular WordPress media-management plugin, hundreds of thousands of installs
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.8%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy