Skip to content
Laskyr

PHP object injection in WordPress plugins

PHP object injection happens when a plugin unserializes data an attacker controls. On its own it often does nothing. It becomes dangerous when another plugin or theme on the same site contains a “gadget”, a piece of code that does something risky when such an object is loaded.

With a usable gadget this can lead to deleting files, reading data or running code. Many records say “no known gadget chain in the plugin itself”, which lowers the risk but does not remove it, because your other plugins count too.

What to do: update the plugin. Keep the total number of plugins down; every extra plugin is extra code an attacker might use.

Worried a plugin bug was used on your site?

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Newest PHP object injection records

486 on record for the plugins we track; the newest 100 are below. Data as of 2026-11-04.

“Affected” is the version range the source gives. “Fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. Each CVE id links to the full record on the plugin’s page.

Other types

Browse vulnerabilities

Where this data comes from

← Check a plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit