Is hl-twitter (WordPress plugin) vulnerable?

WordPress hl-twitter has 3 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

3advisories
0critical
0on CISA KEV
3no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2024-3630The HL Twitter WordPress plugin through 2014.1.18 does not sanitise and escape some of its settings, which could allow high privilege users medium5.4<=2014.1.18–
CVE-2024-3631The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check when unlinking twitter accounts, which could allow attackers to mmedium4.3<=2014.1.18–
CVE-2024-3629The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check in place when updating its settings, which could allow attackers low2.4<=2014.1.18–

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.