dbcve.org
Post Grid ComboWordPress extension · Pickplugins

CVE-2023-6645

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to after 2.2.64 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 Post Grid Combo – 36+ Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the custom JS parameter in all versions up to, and including, 2.2.64 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or higher to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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.64) contains a stored XSS vulnerability in the custom JS parameter. Authenticated users with contributor-level access or higher can inject arbitrary JavaScript because the plugin fails to sanitize input and escape output when handling the custom JS parameter.

MitigationUpdate the plugin to version 2.2.65 or later. If an update is unavailable, review and restrict user roles to prevent contributor-level access, or implement firewall rules at the WAF level to block malicious parameter injection.

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

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 plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Pickplugins Post Grid Combo' in the installed plugins list
    Affected if The plugin is installed and active
  2. Check the installed version
    In the Plugins list, find the version number listed under the plugin name; compare it to the affected range <= 2.2.64
    Affected if The installed version is 2.2.64 or lower
  3. Identify users with contributor-level access
    Go to WordPress admin > Users and review each user role; contributors and users with higher roles (authors, editors, admins) have access to the vulnerable feature
    Affected if There are active users with contributor, author, or editor roles
  4. Inspect custom JS settings
    Navigate to Post Grid Combo plugin settings pages and look for any fields labeled 'custom JS', 'custom code', or similar JavaScript injection options
    Affected if The custom JS parameter field exists and can be accessed by contributor-level users

You are affected if the plugin is installed with version 2.2.64 or lower AND contributor-level or higher users exist who can access the custom JS parameter.

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 2.2.64
Interim mitigation

Update the plugin to version 2.2.65 or later. If an update is unavailable, review and restrict user roles to prevent contributor-level access, or implement firewall rules at the WAF level to block malicious parameter injection.

Recommended fix Moderate confidence

Version 2.2.65 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Post Grid Combo plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the patched version from the WordPress plugin repository

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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