dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1942

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 unauthorized modification of data due to a missing capability check on the b2s_curation_draft AJAX action in all versions up to, and including, 8.7.4. The curationDraft() function only verifies current_user_can('read') without checking whether the user has edit_post permission for the target post. Combined with the plugin granting UI access and nonce exposure to all roles, this makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the title and content of arbitrary posts and pages by supplying a target post ID via the 'b2s-draft-id' parameter.

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 fails to properly validate user capabilities in the curationDraft() AJAX function. It only checks if the user can 'read' rather than verifying 'edit_post' permission for the target post specified in the 'b2s-draft-id' parameter. Combined with nonce exposure and UI access granted to all roles, this IDOR vulnerability allows any authenticated user with Subscriber-level access or higher to modify the title and content of arbitrary posts.

MitigationUpdate to version 8.7.5 or later which includes proper capability validation, or temporarily restrict the b2s_curation_draft AJAX action to users with edit_posts capability pending an update.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Confirm Blog2Social plugin is installed
    Check the WordPress plugins directory for the Blog2Social plugin, typically at /wp-content/plugins/blog-2-social/ or via the WordPress admin plugins list
    Affected if Plugin is installed and active
  2. Identify the installed Blog2Social version
    Read the main plugin file (usually blog-2-social.php) in the plugin directory and locate the version comment/header, or query via WP-CLI: wp plugin list --name=blog-2-social
    Affected if Version is lower than 8.7.5 (the patched version)
  3. Verify the vulnerable AJAX action is exposed
    Check if the b2s_curation_draft AJAX action is registered and publicly accessible by inspecting the plugin source for add_action('wp_ajax_b2s_curation_draft', ...) calls
    Affected if The AJAX action exists and is hooked without edit_posts capability check
  4. Confirm low-privilege user access to the AJAX endpoint
    Test or inspect code to verify that users with Subscriber role can access the b2s_curation_draft AJAX endpoint (the plugin grants UI access to all roles)
    Affected if Subscriber-level or higher users can access the curationDraft() function

If Blog2Social is installed with version lower than 8.7.5 and the b2s_curation_draft AJAX action is accessible to low-privilege users, the environment is affected by this IDOR vulnerability.

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 8.7.5 or later which includes proper capability validation, or temporarily restrict the b2s_curation_draft AJAX action to users with edit_posts capability pending an update.

Recommended fix High confidence

8.7.5 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate Blog2Social: Social Media Auto Post & Scheduler
  4. 4. If an update is available, click 'Update Now' to install version 8.7.5 or later
  5. 5. Verify the update completed successfully
  6. 6. Test that the plugin functionality works as expected after the 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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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