dbcve.org
Postx Gutenberg Blocks For Post GridWordPress extension · Wpxpo

CVE-2021-24659

MEDIUM · 5.4 CVSS v3.1 Published 2021-09-27
Fix available
A fix is available. Upgrade to 2.4.10 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The PostX – Gutenberg Blocks for Post Grid WordPress plugin before 2.4.10 allows users with a role as low as Contributor to perform Stored Cross-Site Scripting attacks via the plugin's block.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The PostX – Gutenberg Blocks for Post Grid WordPress plugin before version 2.4.10 contains a stored Cross-Site Scripting (XSS) vulnerability. The flaw allows authenticated users with Contributor-level permissions to inject malicious JavaScript code through the plugin's Gutenberg blocks, which is then stored and executed when other users view the affected content.

MitigationUpdate the PostX – Gutenberg Blocks for Post Grid plugin to version 2.4.10 or later to remediate this vulnerability. Additionally, review user permissions and consider limiting contributor-level users' ability to publish content until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Postx Gutenberg Blocks For Post GridWordPress extension
Affected:< 2.4.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify PostX plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for the 'postx' or 'postx-gutenberg-blocks' folder
    Affected if The PostX plugin folder exists in the WordPress installation
  2. Check installed PostX version
    In WordPress admin, go to Plugins > Installed Plugins > PostX - Gutenberg Blocks for Post Grid and view the version number; alternatively, check the main plugin PHP file for the 'Version' header in the plugin directory
    Affected if Version is less than 2.4.10 or no version is displayed
  3. Identify user roles with Contributor-level access
    In WordPress admin, go to Users > All Users and review the role assigned to each user; check if any users have the Contributor role specifically
    Affected if Any user with Contributor role or higher exists on the site
  4. Inspect PostX Gutenberg blocks for suspicious content
    Edit pages/posts containing PostX blocks using the Gutenberg editor; examine the block settings and content fields for unexpected script tags, event handlers (onclick, onload, onerror), or encoded JavaScript payloads
    Affected if PostX blocks contain unescaped HTML/script tags or JavaScript event handlers in titles, URLs, or custom fields

A user is affected if the PostX plugin version is below 2.4.10 AND users with Contributor-level permissions exist who can create or edit PostX blocks, as the vulnerability allows stored XSS injection through those blocks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.10 or later
Fixed in 2.4.10
Interim mitigation

Update the PostX – Gutenberg Blocks for Post Grid plugin to version 2.4.10 or later to remediate this vulnerability. Additionally, review user permissions and consider limiting contributor-level users' ability to publish content until the update is applied.

Recommended fix High confidence

2.4.10

  1. Backup your WordPress site database and files before making any changes
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate 'PostX – Gutenberg Blocks for Post Grid' in the plugin list
  5. If an update is available, click 'Update Now' to install version 2.4.10
  6. Alternatively, download version 2.4.10 from the WordPress plugin repository and manually upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin version shows 2.4.10
  8. Test that the plugin blocks function correctly and that the XSS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Postx Gutenberg Blocks For Post Grid Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-24659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-24659 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data