CVE-2024-3239: The Post Grid Gutenberg Blocks and WordPress Blog Plugin WordPress plugin before 4.0.2 does not validate and

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

postx: upgrade to 4.0.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-3239 being exploited?

CVE-2024-3239 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-3239 affect?

CVE-2024-3239 affects postx. Severity is medium (CVSS 5.4). The Post Grid Gutenberg Blocks and WordPress Blog Plugin WordPress plugin before 4.0.2 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with

Q: How urgent is CVE-2024-3239?

Priority 33/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

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

The Post Grid Gutenberg Blocks and WordPress Blog Plugin WordPress plugin before 4.0.2 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-05-14
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wpxpo

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

Am I affected?

Timeline

2024-05-14 15:40 UTCPublished CVE record published
2026-06-17 07:43 UTCUpdated Record last modified

wpxpo postx UPGRADE

Affected: < 4.0.2

Fixed in: 4.0.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy postx || rpm -q postx || postx --version

2. UPGRADE to 4.0.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade postx

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade postx

Note

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

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-3239?

postx: upgrade to 4.0.2. Exact commands for each OS are on this page.

Is CVE-2024-3239 being exploited?

CVE-2024-3239 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-3239 affect?

CVE-2024-3239 affects postx. Severity is medium (CVSS 5.4). The Post Grid Gutenberg Blocks and WordPress Blog Plugin WordPress plugin before 4.0.2 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with

How urgent is CVE-2024-3239?

Priority 33/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-50443 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPXPO Po
CVE-2024-4305 MEDIUM 6.8 UPGRADE The Post Grid Gutenberg Blocks and WordPress Blog Plugin WordPress plugin before 4.1.0 does not validate and
CVE-2024-31246 MEDIUM 5.4 UPGRADE Missing Authorization vulnerability in WPXPO PostX ultimate-post allows Exploiting Incorrectly Configured Acce
CVE-2024-10728 HIGH 8.8 UPGRADE The Post Grid Gutenberg Blocks and WordPress Blog Plugin – PostX plugin for WordPress is vulnerable to unautho

References

← Back to latest CVEs