CVE-2025-12560

Blog2Social: Social Media Auto Post & Scheduler <= 8.6.0 - Authenticated (Subscriber+) Blind Server-Side Request Forgery via post_url

2025-11-05 17:30
LionTree

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-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2025-12560
View all Blog2Social: Social Media Auto Post & Scheduler vulnerabilities

At a glance

CVE-2025-12560 is a medium-severity Server-Side Request Forgery (SSRF) 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). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 8.6.1; sites on affected versions should update now. Disclosed November 2025, reported by LionTree.

Vulnerability Overview

The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 8.6.0 via the getFullContent() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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-918: Server-Side Request Forgery (SSRF)

Blog2Social <= 8.6.0 carries this weakness at getFullContent(), and reaching it takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. 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?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Blog2Social 8.6.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12560https://www.wordfence.com/threat-intel/vulnerabilities/id/2ea06520-d7a9-49bb-812e-2fa2e50d0ec2https://nvd.nist.gov/vuln/detail/CVE-2025-12560

Related records

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