Is landing-pages (WordPress plugin) vulnerable?

WordPress landing-pages has 5 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

5advisories
0critical
0on CISA KEV
4no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2015-4065Cross-site scripting (XSS) vulnerability in shared/shortcodes/inbound-shortcodes.php in the Landing Pages plugin before 1.8.5 for WordPress low3.5<=1.8.4–
CVE-2015-4064SQL injection vulnerability in modules/module.ab-testing.php in the Landing Pages plugin before 1.8.5 for WordPress allows remote authenticamedium6.5<=1.8.4–
CVE-2015-5227The Landing Pages plugin before 1.9.2 for WordPress allows remote attackers to execute arbitrary code via the url parameter.high8.8<=1.9.1–
CVE-2013-6243SQL injection vulnerability in the Landing Pages plugin 1.2.3, before 20131009, and earlier for WordPress allows remote attackers to executehigh7.5<=1.2.3 or =1.0.3.7 or =1.0.3.8 or =1.0.3.9 or =1.0.4.1 or =1.0.4.2 or =1.0.4.4 or =1.0.5.1 or =1.0.5.3 or =1.0.5.6 or =1.0.7.1 or =1.0.7.3 or =1.0.7.9 or =1.0.8.1 or =1.0.8.4 or =1.0.8.5 or =1.0.8.6 or =1.0.9.0 or =1.0.9.3 or =1.0.9.4 or =1.0.9.9 or =1.1 or =1.1.0.1 or =1.1.7 or =1.1.8 or =1.1.9 or =1.2.1–
CVE-2015-10090A vulnerability, which was classified as problematic, has been found in Landing Pages Plugin up to 1.8.7 on WordPress. Affected by this issulow3.5<1.8.81.8.8

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.