CVE-2024-12734: The Advance Post Prefix WordPress plugin through 1.1.1, Advance Post Prefix WordPress plugin through 1.1.1 doe

Q: How do I fix CVE-2024-12734?

advance post prefix: upgrade to newer than 1.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-12734 being exploited?

CVE-2024-12734 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-12734 affect?

CVE-2024-12734 affects advance post prefix. Severity is medium (CVSS 6.1). 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 parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which cou

Q: How urgent is CVE-2024-12734?

Priority 38/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2024-12734 is a medium-severity flaw (CVSS 6.1) affecting advance post prefix. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-05-15
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: niceit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-15 20:15 UTCPublished CVE record published
2026-06-17 07:00 UTCUpdated Record last modified

niceit advance post prefix UPGRADE

Affected: <= 1.1.1

Fixed in: newer than 1.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy advance-post-prefix || rpm -q advance-post-prefix || advance-post-prefix --version

2. UPGRADE to newer than 1.1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade advance-post-prefix

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade advance-post-prefix

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: Advance Post Prefix WordPress plugin - Reflected XSS

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-12734?

advance post prefix: upgrade to newer than 1.1.1. Exact commands for each OS are on this page.

Is CVE-2024-12734 being exploited?

CVE-2024-12734 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-12734 affect?

CVE-2024-12734 affects advance post prefix. Severity is medium (CVSS 6.1). 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 parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which cou

How urgent is CVE-2024-12734?

Priority 38/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-12735 HIGH 7.2 UPGRADE The Advance Post Prefix WordPress plugin through 1.1.1 does not sanitize and escape a parameter before using i

References

← Back to latest CVEs