WordPress plugin · blog2social
Is Blog2Social safe?
Safe on 9.1.5 or newer.
The current version, 9.1.5, is past every affected range on record (28 of 29 records list one; 1 doesn’t, so check it below). Keep it updated and you’re clear of them.
- Flaws on record
- 29
- High or critical
- 6
- Exploited
- none
- Current version
- 9.1.5
- Last updated
- Oct 12, 2026
- Active installs
- 40,000+
Every recorded flaw
- Oct 15, 2026Blog2Social – Social Media Auto Post & Scheduler: Insecure Direct Object ReferenceCVE-2026-108092 · affects up to 9.1.4 · reported by WordfenceMedium 4.3
- Sep 25, 2026Blog2Social: Social Media Auto Post & Scheduler: Authorization bypassCVE-2026-92829 · affects up to 9.1.0 · reported by WordfenceMedium 4.3
- Sep 16, 2026Adenion Blog2Social plugin for WordPress before 9.1.0 allows low-privileged users to modify the scheduled post records of other users.CVE-2026-89031 · fixed in 9.1.0 · reported by VulnCheckMedium 5.3
- Sep 16, 2026Adenion Blog2Social plugin for WordPress before 9.1.0 exposes the email addresses of all registered WordPress users to low-privileged accounts.CVE-2026-89030 · fixed in 9.1.0 · reported by VulnCheckMedium 5.3
- Sep 16, 2026Adenion Blog2Social plugin for WordPress before 9.1.0 allows low-privileged users to enumerate WordPress user accounts.CVE-2026-89029 · fixed in 9.1.0 · reported by VulnCheckMedium 5.3
- Jun 26, 2026Unauthenticated Cross Site Scripting (XSS) in Blog2Social <= 8.9.2 versions.CVE-2026-56044 · reported by PatchstackHigh 7.1
- May 13, 2026Blog2Social: Social Media Auto Post & Scheduler: Missing AuthorizationCVE-2026-7051 · affects up to 8.9.0 · reported by WordfenceMedium 5.4
- Apr 8, 2026Blog2Social: Social Media Auto Post & Scheduler: Authorization bypass through user-controlled keyCVE-2026-4330 · affects up to 8.8.3 · reported by WordfenceMedium 4.3
- Mar 26, 2026Blog2Social: Social Media Auto Post & Scheduler: Unauthorized data lossCVE-2026-4331 · affects up to 8.8.2 · reported by WordfenceMedium 4.3
- Feb 18, 2026Blog2Social: Social Media Auto Post & Scheduler: Unauthorized modification of dataCVE-2026-1942 · affects up to 8.7.4 · reported by WordfenceMedium 6.5
- Jan 10, 2026Blog2Social: Social Media Auto Post & Scheduler: Sensitive Information ExposureCVE-2025-14943 · affects up to 8.7.2 · reported by WordfenceMedium 4.3
- Nov 25, 2025Blog2Social: Social Media Auto Post & Scheduler: Unauthorized modification of dataCVE-2025-13558 · affects up to 8.7.0 · reported by WordfenceMedium 5.4
- Nov 6, 2025Blog2Social: Social Media Auto Post & Scheduler: Server-Side Request ForgeryCVE-2025-12560 · affects up to 8.6.0 · reported by WordfenceMedium 4.3
- Nov 6, 2025Blog2Social: Social Media Auto Post & Scheduler: Limited file uploadCVE-2025-12563 · affects up to 8.6.0 · reported by WordfenceMedium 4.3
- Jun 16, 2025Blog2Social: Social Media Auto Post & Scheduler: SQL InjectionCVE-2025-5673 · affects up to 8.4.4 · reported by WordfenceMedium 6.5
- May 22, 2025Blog2Social: Social Media Auto Post & Scheduler: Does not escape the title of postsCVE-2025-4133 · fixed in 8.4.0 · reported by WPScanMedium 5.4
- Aug 1, 2024Blog2Social: Social Media Auto Post & Scheduler: Stored Cross-Site ScriptingCVE-2024-7302 · affects up to 7.5.4 · reported by WordfenceMedium 6.4
- Jun 11, 2024Blog2Social: Social Media Auto Post & Scheduler: SQL InjectionCVE-2024-3549 · affects up to 7.4.1 · reported by WordfenceCritical 9.9
- Apr 26, 2024Blog2Social: Social Media Auto Post & Scheduler: Sensitive Information ExposureCVE-2024-3678 · affects up to 7.4.2 · reported by WordfenceMedium 5.3
- Oct 20, 2023Blog2Social: Authorization bypassCVE-2022-3622 · affects up to 6.9.11 · reported by WordfenceMedium 4.1
- Sep 6, 2023Unauth.CVE-2023-40554 · affects up to 7.2.0 · reported by PatchstackHigh 7.1
- Aug 21, 2023Blog2Social: Does not sanitise and escape a parameter before outputting it back in the pageCVE-2023-3936 · fixed in 7.2.1 · reported by WPScanMedium 6.1
- Oct 25, 2022Blog2Social: Social Media Auto Post & Scheduler: Does not have authorisation in an AJAX actionCVE-2022-3247 · fixed in 6.9.10 · reported by WPScanMedium 6.5
- Oct 25, 2022Blog2Social: Social Media Auto Post & Scheduler: Does not properly sanitise and escape a parameter before using it in a SQL statementCVE-2022-3246 · fixed in 6.9.10 · reported by WPScan1.5% oddsHigh 8.8
- Dec 21, 2021Blog2Social: Social Media Auto Post & Scheduler: Does not sanitise and escape the b2sShowByDate parameter before outputting it back in an admin pageCVE-2021-24956 · fixed in 6.8.7 · reported by WPScan1.5% oddsMedium 6.1
- Mar 18, 2021Unvalidated input in the Blog2Social WordPress plugin, versions before 6.3.1, lead to SQL Injection in the Re-Share Posts feature, allowing authenticated users CVE-2021-24137 · fixed in 6.3.1 · reported by WPScan1.5% oddsHigh 8.8
- Nov 13, 2019The Blog2Social plugin before 5.9.0 for WordPress is affected by: Cross Site Scripting (XSS).CVE-2019-17550 · fixed in 5.9.0 · reported by MITRE1.3% oddsMedium 6.1
- Aug 1, 2019The Adenion Blog2Social plugin through 5.5.0 for WordPress allows SQL Injection.CVE-2019-13572 · affects up to 5.5.0 · reported by MITRE2.2% oddsCritical 9.8
- Mar 5, 2019The Blog2Social plugin before 5.0.3 for WordPress allows wp-admin/admin.php?page=blog2social-ship XSS.CVE-2019-9576 · fixed in 5.0.3 · reported by MITRE1.4% oddsMedium 6.1
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.