CVE-2025-49438

7.2

Max Chirkov · Simple Login Log

A deserialization of untrusted data vulnerability in the Simple Login Log WordPress plugin allows for PHP object injection.

Executive summary

The Simple Login Log WordPress plugin contains a deserialization vulnerability that could allow an unauthenticated attacker to achieve remote code execution.

Vulnerability

The vulnerability is a deserialization of untrusted data (CWE-502) within the plugin, which allows an unauthenticated attacker to perform PHP object injection. This occurs because the application fails to safely handle user-supplied serialized data, potentially leading to arbitrary code execution.

Business impact

Successful exploitation of this vulnerability poses a severe risk to organizational infrastructure. Because object injection often leads to remote code execution, an attacker could gain full control over the web server, leading to data exfiltration, total system compromise, or the deployment of persistent backdoors. With a CVSS score of 7.2, this vulnerability is classified as High, reflecting the significant potential for impact on confidentiality, integrity, and availability.

Remediation

Immediate Action: Since no official patch is currently available, administrators should immediately deactivate and uninstall the Simple Login Log plugin from all WordPress environments until a secure version is released by the vendor.

Proactive Monitoring: Security teams should review web server access logs for suspicious serialized strings or unusual payload patterns targeting the plugin's endpoints.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules specifically configured to detect and block serialized PHP objects in HTTP requests to help mitigate the risk of exploit attempts.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the critical nature of PHP object injection flaws, immediate removal of the affected plugin is the only effective way to eliminate this attack vector. Organizations should prioritize decommissioning this software until the developer provides a verified security update that addresses the underlying deserialization flaw.

Sources

Originally found and disclosed by mcdruid (Patchstack Alliance), per the CVE Program record.