CVE-2026-54806

WP Activity Log <= 5.6.3.1 - Unauthenticated PHP Object Injection

2026-06-16 00:00
daroo

Strategic Overview

Status
Patched in 5.6.4
Affected Plugin
WP Activity Log
Affected Version
<= 5.6.3.1
CVSS
8.1High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2026-54806
View all WP Activity Log vulnerabilities

At a glance

CVE-2026-54806 is a high-severity Deserialization of Untrusted Data vulnerability in the WP Activity Log WordPress plugin, affecting versions <= 5.6.3.1. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.6.4; sites on affected versions should update now. Disclosed June 2026, reported by daroo.

Vulnerability Overview

The WP Activity Log plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 5.6.3.1 via deserialization of untrusted input. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

Reaching this weakness in WP Activity Log <= 5.6.3.1 takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For WP Activity Log the fix is 5.6.4: builds <= 5.6.3.1 are affected, anything from 5.6.4 onward is not.

Remediation

Update to version 5.6.4, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP Activity Log 5.6.4 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2026-54806https://www.wordfence.com/threat-intel/vulnerabilities/id/cb7f78b8-670f-4a23-9498-6fa570833642https://nvd.nist.gov/vuln/detail/CVE-2026-54806

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C