CVE-2025-60215

8.8

designthemes · Kriya

A deserialization of untrusted data vulnerability in the designthemes Kriya WordPress theme allows for PHP object injection by authenticated users.

Executive summary

A critical deserialization vulnerability in the Kriya theme for WordPress allows authenticated attackers to perform object injection, potentially leading to full system compromise.

Vulnerability

The vulnerability is classified as CWE-502, Deserialization of Untrusted Data, which allows an authenticated user to inject malicious PHP objects into the application. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms that this attack is network-exploitable with low complexity, requiring only low-level privileges to achieve a total impact on confidentiality, integrity, and availability.

Business impact

Successful exploitation of this flaw can lead to unauthorized code execution within the WordPress environment, granting the attacker control over the application. Given the CVSS score of 8.8, this vulnerability poses a severe risk of data theft, site defacement, or the establishment of persistent backdoors, which could result in significant operational disruption and reputational damage.

Remediation

Immediate Action: Since no patch is currently confirmed, administrators should immediately deactivate or remove the Kriya theme until a security update is released by the vendor.

Proactive Monitoring: Review web server access logs for suspicious POST requests containing serialized PHP objects or anomalous activity originating from authenticated user accounts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block serialized PHP objects in HTTP requests to neutralize potential injection attempts.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the high severity of this object injection vulnerability, organizations must treat this as a priority. If the Kriya theme is currently in use, it should be disabled immediately to prevent potential exploitation. Security teams should monitor the vendor's security portal for the release of a patched version and apply it as soon as it becomes available.

More designthemes CVEs

Sources

Originally found and disclosed by Bonds | Patchstack Bug Bounty Program, per the CVE Program record.