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

Published May 30, 2024
·
Updated

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 'postxpresetscallback' 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.

Affected Software

2 affected components
PostX PostX<=4.1.2
WordPress WordPress

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade WordPress plugin – Post Grid Gutenberg Blocks and WordPress Blog Plugin (PostX) to a version that resolves this vulnerability.

    Fixed in 4.1.2
  2. Compensating control

    Prevent Contributor-level (and above) users from being able to reach the vulnerable functionality; restrict access to the WordPress plugin’s affected request/endpoint so only authorized administrators can perform preset/options updates.

Event History

May 30, 2024
CVE Published
via MITRE·10:59 AM
Data Sourced
via MITRE·10:59 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2024-5326?

CVE-2024-5326 is considered a high-severity vulnerability due to unauthorized data modification risks.

2

How do I fix CVE-2024-5326?

To fix CVE-2024-5326, update the PostX plugin to the latest version beyond 4.1.2.

3

What versions of PostX are affected by CVE-2024-5326?

CVE-2024-5326 affects all versions of the PostX plugin up to and including 4.1.2.

4

What impact does CVE-2024-5326 have on WordPress sites?

CVE-2024-5326 could allow unauthorized users to modify site data, jeopardizing site integrity.

5

Is there a workaround for CVE-2024-5326?

Currently, the best workaround for CVE-2024-5326 is to disable the PostX plugin until it is updated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203