dbcve.org
The Post GridWordPress extension · Radiustheme

CVE-2024-35739

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 7.7.2 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in RadiusTheme The Post Grid the-post-grid.This issue affects The Post Grid: from n/a through <= 7.7.1.

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 · moderate confidence

Stored XSS vulnerability in the WordPress 'The Post Grid' plugin allows injection of malicious scripts through unsanitized user input that gets rendered in web pages. The vulnerability exists in versions up to 7.7.1 due to improper input neutralization during page generation.

MitigationUpdate the plugin to the latest version which includes proper input sanitization and output escaping. Alternatively, implement context-aware output encoding at all points where user data is rendered in the application.

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
The Post GridWordPress extension
Affected:< 7.7.2

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 The Post Grid plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Radiustheme The Post Grid' or check the file /wp-content/plugins/the-post-grid/plugin.php exists
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find The Post Grid and note the version number displayed under the plugin name. Alternatively, read the 'Version:' field in the plugin header comment in /wp-content/plugins/the-post-grid/plugin.php
    Affected if Version number is less than 7.7.2 (for example: 7.7.1, 7.7.0, 7.6.x, etc.)
  3. Identify plugin shortcode or widget usage
    Search post/page content or widgets for [the_post_grid] shortcode or check Appearance > Widgets for 'The Post Grid' widget instances
    Affected if The plugin shortcode or widget is actively used on the site, allowing injected scripts to render
  4. Confirm unsanitized input vectors are present
    Access plugin settings at The Post Grid > All Post Grids > Add New and examine fields such as post title, custom CSS, or other user-supplied input fields that accept text and are rendered in frontend output
    Affected if Plugin settings allow free-form text input that is not validated or sanitized and these settings are displayed on public pages

You are affected if The Post Grid plugin is installed with version 7.7.1 or lower AND the plugin shortcode/widget is used on publicly accessible pages, as unsanitized user input can execute malicious scripts in visitor browsers.

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 7.7.2 or later
Fixed in 7.7.2
Interim mitigation

Update the plugin to the latest version which includes proper input sanitization and output escaping. Alternatively, implement context-aware output encoding at all points where user data is rendered in the application.

Recommended fix Moderate confidence

The Post Grid version 7.7.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find "The Post Grid" in the plugin list
  4. Check if current version is below 7.7.2
  5. If update available, click "Update Now" to upgrade to version 7.7.2 or later
  6. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin

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

Fix this in The Post Grid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35739 — 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-2024-35739 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