Live › vulnerability › CVE-2026-114422
The Enable Media Replace WordPress plugin deserializes stored metadata without restricting which PHP classes it can create, so an unauthenticated user can inject a PHP object. When a user with upload access runs a media replacement, the object is instantiated, enabling local file inclusion and, where an attacker-influenced PHP or HTML file exists on the server, remote code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 06:28 UTC. All times on this page are UTC.
Any WordPress site running Enable Media Replace before 4.2.3 is exposed. The risk is highest where users with upload access perform media replacements and where the server holds PHP or HTML files an attacker could influence. Sites without the plugin installed are not affected.
No product ranges from the sources yet.
4.2.3 is affected.4.2.3 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-114422")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.