dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-5326

HIGH · 8.8 CVSS v3.1 Published 2024-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 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 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 PostX WordPress plugin has a broken access control vulnerability in versions up to 4.1.2. The 'postx_presets_callback' function, which modifies WordPress options, lacks a capability check, allowing any authenticated user with Contributor-level access or higher to call it. Attackers can exploit this to enable user registration and set the default new user role to Administrator, achieving privilege escalation.

MitigationUpdate to version 4.1.3 or later when available. Until then, disable the plugin or restrict user registration; consider reviewing user accounts for unauthorized administrators.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Confirm PostX plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or check the /wp-content/plugins/ directory for the postx folder
    Affected if PostX plugin is present on the WordPress installation
  2. Identify installed PostX version
    In Plugins list page, look under the PostX plugin name for the version number, or read the main plugin PHP file header in /wp-content/plugins/postx/
    Affected if Version is 4.1.2 or lower (any version up to and including 4.1.2)
  3. Verify user registration is enabled
    Go to WordPress admin > Settings > General > "Membership" section, or inspect the 'users_can_register' option in wp_options table
    Affected if "Anyone can register" checkbox is checked/enabled
  4. Check default new user role setting
    Go to WordPress admin > Settings > General > "Default Role" dropdown, or inspect the 'default_role' option in wp_options table
    Affected if Default role is set to Administrator
  5. Review user accounts for unauthorized administrators
    Go to WordPress admin > Users list and examine all accounts with Administrator role, or query wp_users and wp_usermeta for administrator-capable users
    Affected if There are administrator accounts you did not create or cannot account for, especially those created recently

If PostX version 4.1.2 or lower is installed AND user registration is enabled AND default role is Administrator AND unexpected admin accounts exist, the environment is likely affected and exploited.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 4.1.3 or later when available. Until then, disable the plugin or restrict user registration; consider reviewing user accounts for unauthorized administrators.

Recommended fix Moderate confidence

PostX version 4.1.3 or later (latest available version)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Post Grid Gutenberg Blocks and WordPress Blog Plugin – PostX'
  4. If update is available, click 'Update Now' to install the latest version
  5. Verify the update completed successfully
  6. Consider changing any site options that may have been modified by attackers

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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