CVE-2024-5326

Post Grid Gutenberg Blocks and WordPress Blog Plugin – PostX <= 4.1.2 - Missing Authorization to Arbitrary Options Update

2024-05-29 00:00
1337_Wannabe

Strategic Overview

Status
Patched in 4.1.3
Affected Plugin
Post Grid Gutenberg Blocks – PostX
Affected Version
<= 4.1.2
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-5326
View all Post Grid Gutenberg Blocks – PostX vulnerabilities

At a glance

CVE-2024-5326 is a high-severity Missing Authorization vulnerability in the Post Grid Gutenberg Blocks WordPress plugin, affecting versions <= 4.1.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 4.1.3; sites on affected versions should update now. Disclosed May 2024, reported by 1337_Wannabe.

Vulnerability Overview

The Post Grid Gutenberg Blocks and WordPress Blog Plugin – PostX plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'postx_presets_callback' function in all versions up to, and including, 4.1.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to change arbitrary options on affected sites. This can be used to enable new user registration and set the default role for new users to Administrator.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Post Grid Gutenberg Blocks <= 4.1.2 carries this weakness at postx_presets_callback, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Post Grid Gutenberg Blocks the fix is 4.1.3: builds <= 4.1.2 are affected, anything from 4.1.3 onward is not.

Remediation

Update to version 4.1.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Post Grid Gutenberg Blocks 4.1.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-5326https://www.wordfence.com/threat-intel/vulnerabilities/id/07a3db33-3787-4b63-835d-8e3026206842https://nvd.nist.gov/vuln/detail/CVE-2024-5326

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C