CVE-2025-12563

Blog2Social: Social Media Auto Post & Scheduler <= 8.6.0 - Incorrect Authorization to Video File Upload

2025-11-05 16:35
thinnawarth mathuros

Strategic Overview

Status
Patched in 8.6.1
Affected Plugin
Blog2Social: Social Media Auto Post & Scheduler
Affected Version
<= 8.6.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-12563
View all Blog2Social: Social Media Auto Post & Scheduler vulnerabilities

At a glance

CVE-2025-12563 is a medium-severity Missing Authorization vulnerability in the Blog2Social WordPress plugin, affecting versions <= 8.6.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 8.6.1; sites on affected versions should update now. Disclosed November 2025, reported by thinnawarth mathuros.

Vulnerability Overview

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to limited file upload due to an incorrect capability check on theuploadVideo() function in all versions up to, and including, 8.6.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload mp4 files to the 'wp-content/uploads/<YYYY>/<MM>/' directory.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Blog2Social <= 8.6.0 carries this weakness at theuploadVideo(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Blog2Social the fix is 8.6.1: builds <= 8.6.0 are affected, anything from 8.6.1 onward is not.

Remediation

Update to version 8.6.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Blog2Social 8.6.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12563https://www.wordfence.com/threat-intel/vulnerabilities/id/3710f139-0f17-426c-b48c-4c42ae4bab5fhttps://nvd.nist.gov/vuln/detail/CVE-2025-12563

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C