CVE-2024-1772 Deserialization in Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio
Authenticated contributors can exploit PHP object injection in the Play.ht WordPress plugin to potentially execute code or access data if a POP chain exists.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-1772?
CVE-2024-1772 is a high-severity unsafe deserialization vulnerability in hammadh Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio, published on 13 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-502
Which versions are affected by CVE-2024-1772?
It affects 1 product.
Products include Hammadh Play.ht.
How do I fix CVE-2024-1772?
No fix has been published for CVE-2024-1772 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2024-1772 being exploited?
There is no known exploitation of CVE-2024-1772 in the wild and no public exploit code.
Other vulnerabilities in hammadh Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio
Sources
Also known as GHSA-hh6q-4r6g-qqjg.