dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-7051

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 8.9.0. This is due to a missing ownership verification in the B2S_Post_Tools::deleteUserPublishPost() and B2S_Post_Tools::deleteUserSchedPost() functions, neither function includes a blog_user_id constraint in its database query, allowing authenticated attackers to soft-delete any user's B2S post records by supplying arbitrary sequential wp_b2s_posts.id values via the 'postId' parameter. This makes it possible for authenticated attackers to delete other users' published and scheduled social media post records, disrupting content publishing workflows.

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 Blog2Social WordPress plugin lacks ownership verification in deleteUserPublishPost() and deleteUserSchedPost() functions. These functions accept a postId parameter but don't validate that the authenticated user owns the corresponding wp_b2s_posts record, allowing any authenticated user to delete any user's social media post entries by manipulating sequential ID values.

MitigationUpdate the Blog2Social plugin to version 8.9.1 or later which adds proper authorization checks. If an update is unavailable, disable the plugin until a patch is released.

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
None
Integrity
Low
Availability
Low

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

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 Blog2Social plugin is installed
    Check the WordPress plugins directory for the blog2social folder, or list active plugins in wp_options table under option_name 'active_plugins'
    Affected if Blog2Social appears in the list of active plugins
  2. Identify the installed Blog2Social version
    Read the version from the plugin's main PHP file header (usually blog2social.php) or from the plugin's readme.txt file in wp-content/plugins/blog2social/
    Affected if Version is lower than 8.9.1 (the patched version)
  3. Verify wp_b2s_posts table exists
    Query the WordPress database: SHOW TABLES LIKE 'wp_b2s_posts'; (table prefix may vary)
    Affected if The table exists and contains post records
  4. Check for multiple user accounts
    Query wp_users table or check WordPress admin Users section to see if more than one user account exists
    Affected if Multiple authenticated users exist in the WordPress installation
  5. Confirm plugin endpoints are accessible
    Check if the plugin's AJAX actions (wp_ajax_deleteUserPublishPost, wp_ajax_deleteUserSchedPost) are registered by examining the plugin's PHP code or testing unauthenticated access returns 403
    Affected if Plugin AJAX handlers are registered and accessible to authenticated users

A user is affected if Blog2Social plugin versions below 8.9.1 are active, the wp_b2s_posts table exists, and multiple user accounts are present in WordPress.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Blog2Social plugin to version 8.9.1 or later which adds proper authorization checks. If an update is unavailable, disable the plugin until a patch is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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