dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-0718

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 for News, Magazines, Blog Websites – PostX plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the ultp_shareCount_callback() function in all versions up to, and including, 5.0.5. This makes it possible for unauthenticated attackers to modify the share_count post meta for any post, including private or draft posts.

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 missing capability check on the ultp_shareCount_callback() function, allowing unauthenticated attackers to modify share_count post meta for any post, including private and draft posts. This is a broken access control vulnerability where the AJAX callback does not verify user permissions before processing requests.

MitigationUpdate to version 5.0.6 or later which adds proper capability checks. If immediate update is not possible, consider disabling the plugin or adding a firewall/WAF rule to block the affected AJAX endpoint.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 PostX plugin installation and version
    Locate the PostX plugin directory (wp-content/plugins/postx or post-x) and read the main plugin file header to find the Version field, or query the WordPress plugins database table for the plugin version.
    Affected if The plugin is installed and the version is lower than 5.0.6 (versions prior to 5.0.6 lack the capability check).
  2. Identify the vulnerable AJAX endpoint
    Check if the file ultp_shareCount_callback exists within the plugin includes or classes folder, and verify that it is registered as an AJAX action hooked to wp_ajax_ultp_shareCount and wp_ajax_nopriv_ultp_shareCount.
    Affected if The callback function is hooked to wp_ajax_nopriv_ (allowing unauthenticated access), which is the default vulnerable configuration.
  3. Test unauthenticated AJAX access
    Send a POST request to /wp-admin/admin-ajax.php with action=ultp_shareCount and a post_id parameter (such as post_id=1), without providing any authentication cookies or headers.
    Affected if The endpoint returns a successful response without requiring login credentials, indicating the broken access control is present.

A user is affected if the PostX plugin version is below 5.0.6 and the AJAX endpoint responds to unauthenticated requests.

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 5.0.6 or later which adds proper capability checks. If immediate update is not possible, consider disabling the plugin or adding a firewall/WAF rule to block the affected AJAX endpoint.

Recommended fix Moderate confidence

Upgrade to the latest version of PostX plugin (newer than 5.0.5)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the PostX plugin (Post Grid Gutenberg Blocks for News, Magazines, Blog Websites – PostX)
  4. Check the current installed version (ensure it is not 5.0.5 or earlier)
  5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. Verify the update completed successfully
  7. Confirm the new version number after update

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-2026-0718 — 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-2026-0718 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