CVE-2022-3247

Blog2Social <= 6.9.9 - Authenticated (Subscriber+) Server-Side Request Forgery

2022-10-03 00:00
Saggre

Strategic Overview

Status
Patched in 6.9.10
Affected Plugin
Blog2Social: Social Media Auto Post & Scheduler
Affected Version
<= 6.9.9
CVSS
6.8Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2022-3247
View all Blog2Social: Social Media Auto Post & Scheduler vulnerabilities

At a glance

CVE-2022-3247 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Blog2Social WordPress plugin, affecting versions <= 6.9.9. It carries a CVSS score of 6.8 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.9.10; sites on affected versions should update now. Disclosed October 2022, reported by Saggre.

Vulnerability Overview

The Blog2Social plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 6.9.9 due to missing URL validation to ensure an external URL is used in the function b2sFileGetContents. This makes it possible for authenticated users, with subscriber-level access or higher, to perform attacks against the server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. A successful exploit has high impact on confidentiality.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Blog2Social <= 6.9.9 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 6.9.10: builds <= 6.9.9 are affected, anything from 6.9.10 onward is not.

Remediation

Update to version 6.9.10, 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 6.9.10 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-3247https://www.wordfence.com/threat-intel/vulnerabilities/id/25baf78e-e9bc-421b-8a66-9571ac3625c3https://nvd.nist.gov/vuln/detail/CVE-2022-3247

Related records

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