# 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.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hh6q-4r6g-qqjg

## 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 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-1772?

It affects 1 product.


Products: 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.

## 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

- [CVE-2024-0828](https://insights.sbomify.com/CVE-2024-0828/): Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio <= 3.6.4 - Missing Authorization (medium 5.4)
- [CVE-2024-0827](https://insights.sbomify.com/CVE-2024-0827/): Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio <= 3.6.4 - Cross-Site Request Forgery (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1772 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2024-1772 in the wild and no public exploit code.

Affected product: hammadh Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1772/ (Markdown: https://insights.sbomify.com/CVE-2024-1772/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1772
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1772
- OSV: https://osv.dev/vulnerability/CVE-2024-1772

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1772/
Summaries are generated and may contain mistakes; the official description above is the record.