<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: hammadh</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-1772: The Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio plugin for WordPress is vulnerable to </title><link>https://patchthecve.com/cve/CVE-2024-1772.html</link><guid>https://patchthecve.com/cve/CVE-2024-1772.html</guid><pubDate>Wed, 17 Jun 2026 07:04:58 +0000</pubDate><description>HIGH 8.8: 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 attacke</description></item><item><title>CVE-2024-0828: The Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio plugin for WordPress is vulnerable to </title><link>https://patchthecve.com/cve/CVE-2024-0828.html</link><guid>https://patchthecve.com/cve/CVE-2024-0828.html</guid><pubDate>Wed, 17 Jun 2026 06:54:23 +0000</pubDate><description>MEDIUM 5.4: The Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio plugin for WordPress is vulnerable to unauthorized access of functionality due to a missing capability check on several functions in all versions up to, and including, 3.6.4. This makes it possible for authenticated attackers, w</description></item><item><title>CVE-2024-0827: The Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio plugin for WordPress is vulnerable to </title><link>https://patchthecve.com/cve/CVE-2024-0827.html</link><guid>https://patchthecve.com/cve/CVE-2024-0827.html</guid><pubDate>Wed, 17 Jun 2026 06:54:23 +0000</pubDate><description>MEDIUM 4.3: The Play.ht – Make Your Blog Posts Accessible With Text to Speech Audio plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.6.4. This is due to missing or incorrect nonce validation on several functions. This makes it possible for unauthenticated </description></item></channel></rss>