Is advance-post-prefix (WordPress plugin) vulnerable?

WordPress advance-post-prefix has 2 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

2advisories

0critical

0on CISA KEV

2no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2024-12735	The Advance Post Prefix WordPress plugin through 1.1.1 does not sanitize and escape a parameter before using it in a SQL statement, allowing	high	7.2	`<=1.1.1`	–
CVE-2024-12734	The Advance Post Prefix WordPress plugin through 1.1.1, Advance Post Prefix WordPress plugin through 1.1.1 does not sanitise and escape a pa	medium	6.1	`<=1.1.1`	–

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.