dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13558

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-25
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 unauthorized modification of data due to a missing capability check on the 'deleteUserCcDraftPost' function in all versions up to, and including, 8.7.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change the status of arbitrary posts to trash.

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 versions up to 8.7.0 lacks a capability check on the 'deleteUserCcDraftPost' function, allowing any authenticated user with Subscriber-level privileges to modify post statuses and trash arbitrary posts they do not own. This is a Broken Access Control (IDOR) vulnerability.

MitigationUpdate the Blog2Social plugin to version 8.7.1 or later which includes proper capability validation. Until patched, consider restricting user registration or using a WAF to mitigate exploitation.

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. Identify if Blog2Social plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for Blog2Social, or check the /wp-content/plugins/ directory for the blog2social folder
    Affected if The plugin is installed and the version is 8.7.0 or lower
  2. Determine the installed version of Blog2Social
    In WordPress admin > Plugins > Installed Plugins, find Blog2Social and note the version number displayed below the plugin name
    Affected if The version listed is 8.7.0 or any version below 8.7.1 (e.g., 8.6.9, 8.5.0, etc.)
  3. Verify the Subscriber role exists on the site
    Go to WordPress admin > Users > Users and look for the 'Subscriber' role in any user row, or use a user role editor plugin to list all roles
    Affected if The Subscriber role is present in the WordPress installation
  4. Check if any users have Subscriber-level access
    In WordPress admin > Users > Users, filter or search for users with the Subscriber role, or check the wp_usermeta table for meta_key='wp_capabilities' containing 'subscriber'
    Affected if There is at least one user account with Subscriber role (even a newly registered account)
  5. Confirm the vulnerable function exists in the plugin code
    Access the WordPress files via FTP or file manager, navigate to /wp-content/plugins/blog2social/includes/, and search for the function 'deleteUserCcDraftPost' in the PHP files
    Affected if The function deleteUserCcDraftPost is found in the plugin code without a capability check (the function exists in versions up to 8.7.0)

You are affected if Blog2Social plugin versions 8.7.0 or below are installed, the Subscriber role exists, and there is at least one Subscriber-level user account on the site.

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 the Blog2Social plugin to version 8.7.1 or later which includes proper capability validation. Until patched, consider restricting user registration or using a WAF to mitigate exploitation.

Recommended fix Moderate confidence

8.7.1 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Blog2Social: Social Media Auto Post & Scheduler plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running on version 8.7.1 or higher
  6. 6. Confirm the vulnerability is remediated by testing that lower-privileged users (Subscriber level) can no longer trash arbitrary posts

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-2025-13558 — 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-2025-13558 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