Blog2Social: Social Media Auto Post & Scheduler <= 6.3.0 - Authenticated SQL Injection
Strategic Overview
- Status
- Patched in 6.3.1
- Affected Plugin
- Blog2Social: Social Media Auto Post & Scheduler
- Affected Version
<= 6.3.0- CVSS
- 8.8High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2021-24137
At a glance
CVE-2021-24137 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Blog2Social WordPress plugin, affecting versions <= 6.3.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 6.3.1; sites on affected versions should update now. Disclosed May 2020, reported by Nguyen Anh Tien.
Vulnerability Overview
Unvalidated input in the Blog2Social WordPress plugin, versions before 6.3.1, lead to SQL Injection in the Re-Share Posts feature, allowing authenticated users to inject arbitrary SQL commands.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in Blog2Social <= 6.3.0 takes any authenticated account. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Blog2Social the fix is 6.3.1: builds <= 6.3.0 are affected, anything from 6.3.1 onward is not.
Remediation
Update to version 6.3.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Blog2Social: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Blog2Social 6.3.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Blog2Social: Social Media Auto Post & Scheduler
- 8.5Blog2Social <= 6.9.3 PHP Object Injection
- 7.4Blog2Social: Social Media Auto Post & Scheduler PHP Object Injection
- 7.2CVE-2026-56044: Blog2Social Stored XSS
CVE-2026-56044 - 6.8CVE-2022-3247: Blog2Social <= 6.9.9 Server-Side Request Forgery
CVE-2022-3247 - 6.5CVE-2026-1942: Blog2Social Authenticated (Subscriber+) Arbitrary Post
CVE-2026-1942 - 6.4CVE-2025-4133: Blog2Social Stored XSS
CVE-2025-4133 - 6.4CVE-2024-7302: Blog2Social Stored XSS
CVE-2024-7302 - 6.1CVE-2023-3936: Blog2Social Reflected XSS
CVE-2023-3936
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C