CVE-2024-1772 HIGH

CVE-2024-1772: Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio <= 3.6.4 - Authenticated (Contributor+) PHP Object Injection

Vendor Hammadh
Product Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio
Weakness CWE-502 · Unsafe deserialization
Published March 13, 2024
Last update April 8, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

The Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.6.4 via deserialization of untrusted input from the play_podcast_data post meta. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable plugin. 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.

Explanation of Vulnerability in Simple Terms

02Summary

Play.ht versions up to 3.6.4 contain a deserialization vulnerability that allows authenticated attackers to execute arbitrary code on the site. The plugin unsafely processes serialized data without proper validation, enabling an attacker with low-level access to inject malicious code. This affects confidentiality, integrity, and availability of the entire site.

What an attacker can do

03Attacker Capabilities

Run arbitrary code on the site with full access to the database and files.

Potential impact on your site

04Site Impact

A compromised user account can lead to complete site takeover, data theft, or malware injection.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account (subscriber or contributor level) on the site.

Key dates

06Disclosure timeline

March 13, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE