Skip to main content

CVE-2026-109555renehermi WP STAGING deserialization of untrusted data

Schedule itHigh8.0EPSS not scored yet

CVE-2026-109555 is a deserialization of untrusted data in renehermi WP STAGING, rated high (8.0 on CVSS 3.1).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Deferred

What it is

Serialized objects from outside are turned back into live objects, which a crafted payload can abuse to run code.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker turn crafted data into code execution inside the receiving service.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place renehermi WP STAGING runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. While there is no fix, review who holds accounts that can reach it.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

The WP STAGING and WP STAGING Pro plugins for WordPress are vulnerable to PHP Object Injection in all versions up to, and including, 4.17.0 and 6.17.0, respectively, via deserialization of untrusted input during database restore and staging reset. This is due to the database importer treating attacker-controlled text beginning with {WPSTG_BINARY} as trusted internal binary data and decoding its hexadecimal suffix into serialized bytes. This makes it possible for authenticated attackers, with Subscriber-level access and above, to plant a malicious serialized object in their own profile. When an Administrator later performs an ordinary database-including restore or staging reset containing that value, and the restored profile metadata is loaded, either during the restore or in a later request, a built-in POP chain can be used to execute arbitrary code on the server. Additional built-in gadget chains allow arbitrary local file read in both WP STAGING and WP STAGING Pro and arbitrary file deletion in WP STAGING Pro. The attacker does not require Administrator credentials or a copy of a backup, but exploitation does require the later privileged restore or reset.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
  • APIs, queues and caches that accept serialized objects. The flaw sits between a message producer and the service that deserializes it.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Between a message producer and the service that deserializes it. An attacker who crosses it can turn crafted data into code execution inside the receiving service.

Questions to answer about your own systems

  • Where does renehermi WP STAGING run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.