dbcve.org
Post Grid ComboWordPress extension · Pickplugins

CVE-2023-7072

HIGH · 7.5 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 2.2.69 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 Post Grid Combo – 36+ Gutenberg Blocks plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.2.68 via the 'get_posts' REST API Endpoint. This makes it possible for unauthenticated attackers to extract sensitive data including full draft posts and password protected posts, as well as the password for password-protected posts.

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 Post Grid Combo WordPress plugin (versions up to 2.2.68) exposes a REST API endpoint (/wp-json/post-grid-combo/v1/get_posts) that fails to properly authorize requests. Unauthenticated attackers can query this endpoint to retrieve draft posts, password-protected posts, and the plaintext passwords for protected content.

MitigationUpdate the Post Grid Combo plugin to version 2.2.69 or later, which contains proper authorization checks for the REST API endpoint.

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
Post Grid ComboWordPress extension
Affected:< 2.2.69

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 plugin installation
    Check if the Pickplugins Post Grid Combo plugin is installed by examining the WordPress plugins directory or the site's plugin list in wp-admin
    Affected if Plugin is present on the WordPress site
  2. Check installed version
    Locate the plugin's main file (typically post-grid-combo.php) and read the Version header comment, or check via wp-admin Plugins page
    Affected if Version is below 2.2.69 (versions up to and including 2.2.68 are affected)
  3. Test vulnerable REST API endpoint
    Send a GET request to /wp-json/post-grid-combo/v1/get_posts without any authentication headers or parameters
    Affected if Endpoint returns a successful response with post data without requiring authentication
  4. Verify sensitive content exposure
    Examine the API response for draft posts, password-protected posts, or plaintext password fields in the returned data
    Affected if The response contains draft posts, password-protected content, or plaintext passwords without having authenticated

User is affected if Post Grid Combo plugin version is below 2.2.69 AND the /wp-json/post-grid-combo/v1/get_posts endpoint responds to unauthenticated requests with sensitive post data

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.2.69 or later
Fixed in 2.2.69
Interim mitigation

Update the Post Grid Combo plugin to version 2.2.69 or later, which contains proper authorization checks for the REST API endpoint.

Recommended fix High confidence

2.2.69

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Post Grid Combo' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.2.69 or later
  5. 5. Alternatively, you can manually download the updated plugin from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version shows 2.2.69 or higher under Plugins > Installed Plugins
  7. 7. Confirm the vulnerability is remediated by verifying the get_posts REST API endpoint no longer returns sensitive data for unauthenticated requests

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

Fix this in Post Grid Combo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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