Libsyn Publisher Hub
libsyn-podcasting · plugin
Known security vulnerabilities for Libsyn Publisher Hub. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
4 exploitable without logging in · latest Apr 15, 2024
Closed on wordpress.org
Removed from the directory on Mar 7, 2024 · reason: security issue. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Medium 6.1
CVE-2023-45835unauthenticated · needs a click≤ 1.4.4
WordPress Libsyn Publisher Hub Plugin <= 1.4.4 is vulnerable to Cross Site Scripting (XSS)
- Medium 5.4
CVE-2024-32140login required≤ 1.4.4
WordPress Libsyn Publisher Hub plugin <= 1.4.4 - Cross Site Scripting (XSS) vulnerability
- Medium 5.3
CVE-2023-25057unauthenticated≤ 1.3.2
WordPress Libsyn Publisher Hub Plugin <= 1.3.2 is vulnerable to Sensitive Data Exposure
- Medium 5.3
CVE-2023-45834unauthenticated≤ 1.4.4
WordPress Libsyn Publisher Hub Plugin <= 1.4.4 is vulnerable to Sensitive Data Exposure
- Medium 4.3
CVE-2024-32141unauthenticated · needs a click≤ 1.4.4
WordPress Libsyn Publisher Hub plugin <= 1.4.4 - Cross Site Request Forgery (CSRF) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).