WordPress plugin · Updated daily · Source: Wordfence Intelligence

Post Grid vulnerabilities: affected versions and fixes

Post Grid has 20,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Post Grid at a glance

  • 28 publicly disclosed vulnerabilities, 8 of them rated High or Critical. The most recent was disclosed on Sep 4, 2026.
  • Ranked #1080 by popularity on WordPress.org (20,000+ active installs).
  • The latest version is 2.3.24 (released Jul 19, 2026). The most recent security fix shipped in 2.3.23.
  • 1 vulnerability has no fix yet. Check the list below to see whether it affects how you use the plugin.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Post Grid version

Enter the Post Grid version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Post Grid”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Post Grid”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.3.24). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Post Grid vulnerabilities (latest 25 of 28)

  • Post Grid and Gutenberg Blocks – ComboBlocks 2.2.85 - 2.3.22 - Unauthenticated Hook Injection

    Other weakness · CVE-2024-11080

    Affected versions: ≥ 2.2.85, ≤ 2.3.22

    Fixed in: 2.3.23

    Severity: Critical 9.8 · Disclosed Sep 4, 2026

  • Post Grid and Gutenberg Blocks <= 2.3.23 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-68605

    Affected versions: ≤ 2.3.23

    Fixed in: 2.3.24

    Severity: Medium 6.4 · Disclosed Dec 21, 2025

  • Post Grid and Gutenberg Blocks <= 2.3.19 - Unauthenticated Insecure Direct Object Reference

    Missing authorization · CVE-2025-63043

    Affected versions: ≤ 2.3.19

    Fixed in: No fix yet

    Severity: Medium 5.3 · Disclosed Dec 3, 2025

  • Post Grid and Gutenberg Blocks <= 2.3.17 - Missing Authorization

    Missing authorization · CVE-2025-62924

    Affected versions: ≤ 2.3.17

    Fixed in: 2.3.18

    Severity: Medium 4.3 · Disclosed Oct 4, 2025

  • Post Grid and Gutenberg Blocks <= 2.3.11 - Authenticated (Contributor+) PHP Object Injection

    PHP object injection · CVE-2025-54007

    Affected versions: ≤ 2.3.11

    Fixed in: 2.3.12

    Severity: High 8.8 · Disclosed Aug 6, 2025

  • Post Grid and Gutenberg Blocks – ComboBlocks <= 2.3.6 - Unauthenticated User Information Exposure

    Information disclosure · CVE-2024-13796

    Affected versions: ≤ 2.3.6

    Fixed in: 2.3.7

    Severity: Medium 5.3 · Disclosed Feb 27, 2025

  • Post Grid and Gutenberg Blocks – ComboBlocks <= 2.3.5 - Unauthenticated Paid Order Creation

    Other weakness · CVE-2024-13798

    Affected versions: ≤ 2.3.5

    Fixed in: 2.3.6

    Severity: Medium 5.3 · Disclosed Feb 21, 2025

  • Post Grid and Gutenberg Blocks 2.2.85 - 2.3.3 - Unauthenticated Privilege Escalation

    Privilege escalation · CVE-2024-9636

    Affected versions: ≥ 2.2.85, ≤ 2.3.3

    Fixed in: 2.3.4

    Severity: Critical 9.8 · Disclosed Jan 14, 2025

  • Post Grid and Gutenberg Blocks <= 2.2.92 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-9645

    Affected versions: ≤ 2.2.92

    Fixed in: 2.2.93

    Severity: Medium 6.4 · Disclosed Jan 14, 2025

  • Post Grid and Gutenberg Blocks <= 2.2.93 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-50432

    Affected versions: ≤ 2.2.93

    Fixed in: 2.2.94

    Severity: Medium 6.4 · Disclosed Oct 24, 2024

  • Post Grid and Gutenberg Blocks <= 2.2.89 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-47340

    Affected versions: ≤ 2.2.89

    Fixed in: 2.2.90

    Severity: Medium 6.4 · Disclosed Sep 27, 2024

  • Post Grid and Gutenberg Blocks 2.2.87 - 2.2.90 - Authenticated (Subscriber+) Privilege Escalation

    Privilege escalation · CVE-2024-8253

    Affected versions: ≥ 2.2.87, ≤ 2.2.90

    Fixed in: 2.2.91

    Severity: High 8.8 · Disclosed Sep 10, 2024

  • Gutenberg Blocks, Page Builder – ComboBlocks <= 2.2.87 - Authenticated (Contributor+) Stored Cross-Site Scripting via Accordion Block

    Cross-site scripting (XSS) · CVE-2024-7588

    Affected versions: ≤ 2.2.84

    Fixed in: 2.2.88

    Severity: Medium 6.4 · Disclosed Aug 13, 2024

  • ComboBlocks <= 2.2.86 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-43155

    Affected versions: ≤ 2.2.86

    Fixed in: 2.2.87

    Severity: Medium 6.4 · Disclosed Aug 7, 2024

  • Post Grid, Form Maker, Popup Maker, WooCommerce Blocks, Post Blocks, Post Carousel – Combo Blocks <= 2.2.85 - Authenticated (Contributor+) Stored Cross-Site Scripting via redirectURL Parameter of Date Countdown Widget

    Cross-site scripting (XSS) · CVE-2024-6346

    Affected versions: ≤ 2.2.85

    Fixed in: 2.2.86

    Severity: Medium 6.4 · Disclosed Jul 31, 2024

  • Post Grid, Form Maker, Popup Maker, WooCommerce Blocks, Post Blocks, Post Carousel - Combo Blocks <= 2.2.80 - Authenticated (Contributor+) Stored Cross-Site Scripting via Block Attribute

    Cross-site scripting (XSS) · CVE-2024-4042

    Affected versions: ≤ 2.2.80

    Fixed in: 2.2.81

    Severity: Medium 6.4 · Disclosed Jun 6, 2024

  • Post Grid, Form Maker, Popup Maker, WooCommerce Blocks, Post Blocks, Post Carousel – Combo Blocks <= 2.2.80 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-3155

    Affected versions: ≤ 2.2.80

    Fixed in: 2.2.81

    Severity: Medium 6.4 · Disclosed May 20, 2024

  • Post Grid, Form Maker, Popup Maker, WooCommerce Blocks, Post Blocks, Post Carousel – Combo Blocks <= 2.2.78 - Unauthenticated Sensitive Information Exposure

    Information disclosure · CVE-2024-32816

    Affected versions: ≤ 2.2.78

    Fixed in: 2.2.79

    Severity: Medium 5.3 · Disclosed Apr 22, 2024

  • Post Grid <= 2.2.74 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-30441

    Affected versions: ≤ 2.2.74

    Fixed in: 2.2.76

    Severity: Medium 6.1 · Disclosed Mar 28, 2024

  • Post Grid, Form Maker, Popup Maker, WooCommerce Blocks, Post Blocks, Post Carousel <= 2.2.74 - Information Exposure

    Missing authorization · CVE-2024-0881

    Affected versions: ≤ 2.2.74

    Fixed in: 2.2.76

    Severity: Medium 5.3 · Disclosed Mar 19, 2024

  • Post Grid Combo – 36+ Gutenberg Blocks <= 2.2.68 - Information Exposure via get_posts API Endpoint

    Information disclosure · CVE-2023-7072

    Affected versions: ≤ 2.2.68

    Fixed in: 2.2.69

    Severity: High 7.5 · Disclosed Mar 12, 2024

  • Post Grid Combo – 36+ Gutenberg Blocks <= 2.2.64 - Authenticated (Contributor+) Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-6645

    Affected versions: ≤ 2.2.64

    Fixed in: 2.2.65

    Severity: Medium 6.4 · Disclosed Dec 15, 2023

  • Post Grid <= 2.2.50 - Missing Authorization to Sensitive Information Exposure via REST API

    Missing authorization · CVE-2023-40211

    Affected versions: ≤ 2.2.50

    Fixed in: 2.2.51

    Severity: High 7.5 · Disclosed Aug 11, 2023

  • Post Grid <= 2.1.15 - Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-24986

    Affected versions: < 2.1.16

    Fixed in: 2.1.16

    Severity: Medium 6.1 · Disclosed Mar 15, 2022

  • Post Grid < 2.1.16 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-0447

    Affected versions: < 2.1.16

    Fixed in: 2.1.16

    Severity: Medium 6.1 · Disclosed Mar 15, 2022

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Sep 4, 2026.

Most common weaknesses in Post Grid

Cross-site scripting (XSS)

14 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

4 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Information disclosure

3 issues

Data that should stay private, such as user details or configuration values, can be read from outside.

Frequently asked questions

Is Post Grid safe to use?

Post Grid is a well-known plugin with 20,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.3.24) and turn on automatic updates. That said, 1 issue has no fix yet, so check the list below.

How do I find which version of Post Grid my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesPost Grid on WordPress.org