Is gigpress (WordPress plugin) vulnerable?

WordPress gigpress has 6 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

6advisories
0critical
0on CISA KEV
3no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2015-4066Multiple SQL injection vulnerabilities in admin/handlers.php in the GigPress plugin before 2.3.9 for WordPress allow remote authenticated usmedium6.5<=2.3.8–
CVE-2015-9353The gigpress plugin before 2.3.11 for WordPress has SQL injection in the admin area, a different vulnerability than CVE-2015-4066.high7.2<2.3.112.3.11
CVE-2023-0381The GigPress WordPress plugin through 2.3.28 does not validate and escape some of its shortcode attributes before using them in SQL statemenhigh8.8<=2.3.28–
CVE-2022-4759The GigPress WordPress plugin before 2.3.28 does not validate and escape some of its shortcode attributes before outputting them back in a pmedium5.4<2.3.282.3.28
CVE-2015-9354The gigpress plugin before 2.3.11 for WordPress has XSS.medium4.8<2.3.112.3.11
CVE-2023-7233The GigPress WordPress plugin through 2.3.29 does not sanitise and escape some of its settings, which could allow high privilege users such medium4.8<=2.3.29–

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.