dbcve.org
The Post GridWordPress extension · Radiustheme

CVE-2023-39923

HIGH · 8.8 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to after 7.2.7 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in RadiusTheme The Post Grid plugin <= 7.2.7 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the RadiusTheme The Post Grid WordPress plugin versions 7.2.7 and below allows attackers to induce authenticated administrators to perform unintended actions by tricking them into submitting malicious requests.

MitigationUpdate the plugin to version 7.2.8 or later which contains the CSRF fix. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block malicious requests.

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.2.7

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate 'The Post Grid' by RadiusTheme in the list. Alternatively, check the wp-content/plugins folder for a directory named 'the-post-grid' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, click on the plugin name to view its details, or inspect the plugin's main PHP file header for the 'Version' field. If using WP-CLI, run: wp plugin list --name='the-post-grid' --format=table
    Affected if The displayed version number is 7.2.7 or lower
  3. Confirm the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, verify that 'The Post Grid' shows as 'Active' (not deactivated or deleted). Check wp_options table for active_plugins option if direct database access is available.
    Affected if The plugin is activated on the site
  4. Identify if admin authentication is in use
    Review WordPress user roles. Navigate to Users > All Users in the admin panel. Confirm that administrator-level accounts exist and are able to access the plugin settings where CSRF-protected actions would be performed.
    Affected if Authenticated administrators have access to the plugin functionality

The environment is affected if the RadiusTheme The Post Grid plugin is installed, active, and running version 7.2.7 or lower, allowingCSRF attacks against authenticated administrators.

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 a release after 7.2.7
Interim mitigation

Update the plugin to version 7.2.8 or later which contains the CSRF fix. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block malicious requests.

Recommended fix Moderate confidence

The Post Grid version 7.2.8 or later (check WordPress plugin repository for current stable release)

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'The Post Grid' by RadiusTheme in the plugin list
  4. Check if an update is available and install the latest version

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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