Blog2Social · Security record

Is Blog2Social safe?

No known vulnerability affects the current version (9.1.7). 34 issues were found in earlier versions and fixed, the latest disclosed on Sep 24, 2026.

Checked 5 days ago against the WPVulnerability database, for version 9.1.7.

How it’s looked after

Last release: Nov 6, 2026 (2 days ago)
Releases in the last year: 28
Tested up to: WordPress 7.1.4
Support resolved: 1 of 1 threads in two months
Active installs: 40K+

34 known vulnerabilities

2 critical
4 high
20 medium
8 not rated

None affects the current version.

Disclosed each year

20181
20194
20202
20211
20224
20232
20243
20255
202611

Every known vulnerability in Blog2Social

Newest first, with any that affect the current version at the top.

medium
Authenticated (Contributor+) Insecure Direct Object Reference to Sensitive Information Exposure
Fixed in 9.1.5 · CVE-2026-108092 · Sep 24, 2026 · Wordfence
medium
Missing Authorization to Authenticated (Contributor+) Arbitrary Modification via Multiple AJAX Handlers
Fixed in 9.1.1 · CVE-2026-92829 · Sep 16, 2026 · Wordfence
medium
Authenticated (Subscriber+) Username Enumeration
Fixed in 9.1.0 · CVE-2026-89029 · Sep 16, 2026 · Wordfence
medium
Missing Authorization
Fixed in 9.1.0 · CVE-2026-89030 · Sep 16, 2026 · Wordfence
medium
Insecure Direct Object Reference
Fixed in 9.1.0 · CVE-2026-89031 · Sep 16, 2026 · Wordfence
high
Unauthenticated Stored Cross-Site Scripting
Fixed in 8.9.3 · CVE-2026-56044 · Jun 25, 2026 · Wordfence
medium
Missing Authorization to Authenticated (Subscriber+) Delete Arbitrary B2S Post Records via 'postId' Parameter
Fixed in 8.9.1 · CVE-2026-7051 · May 12, 2026 · Wordfence
Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Post Schedule Modification via 'b2s_id' Parameter
Fixed in 8.8.4 · CVE-2026-4330 · Apr 7, 2026 · Wordfence
Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Meta Deletion via 'b2s_reset_social_meta_tags' AJAX Action
Fixed in 8.8.3 · CVE-2026-4331 · Mar 25, 2026 · Wordfence
Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Modification
Fixed in 8.7.5 · CVE-2026-1942 · Feb 17, 2026 · Wordfence
medium
Incorrect Authorization to Authenticated (Subscriber+) Sensitive Information Exposure
Fixed in 8.7.3 · CVE-2025-14943 · Jan 9, 2026 · Wordfence
medium
Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Trashing
Fixed in 8.7.1 · CVE-2025-13558 · Nov 24, 2025 · Wordfence
medium
Incorrect Authorization to Video File Upload
Fixed in 8.6.1 · CVE-2025-12563 · Nov 5, 2025 · Wordfence
medium
Authenticated (Subscriber+) Blind Server-Side Request Forgery via post_url
Fixed in 8.6.1 · CVE-2025-12560 · Nov 5, 2025 · Wordfence
medium
Authenticated (Subscriber+) SQL Injection via `prgSortPostType` Parameter
Fixed in 8.4.5 · CVE-2025-5673 · Jun 16, 2025 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 8.4.0 · CVE-2025-4133 · May 1, 2025 · Wordfence
medium
Authenticated (Author+) Stored Cross-Site Scripting via File Upload
Fixed in 7.5.5 · CVE-2024-7302 · Jul 31, 2024 · Wordfence
critical
Authenticated (Subscriber+) SQL Injection
Fixed in 7.4.2 · CVE-2024-3549 · Jun 10, 2024 · Wordfence
medium
Information Exposure
Fixed in 7.5.0 · CVE-2024-3678 · Apr 25, 2024 · Wordfence
high
WordPress Blog2Social Plugin <= 7.2.0 is vulnerable to Cross Site Scripting (XSS)
Fixed in 7.2.1 · CVE-2023-40554 · Aug 16, 2023 · Patchstack
medium
Reflected Cross-Site Scripting
Fixed in 7.2.1 · CVE-2023-3936 · Jul 26, 2023 · Wordfence
high
Authenticated (Subscriber+) SQL Injection
Fixed in 6.9.10 · CVE-2022-3246 · Oct 3, 2022 · Wordfence
medium
Authenticated (Subscriber+) Server-Side Request Forgery
Fixed in 6.9.10 · CVE-2022-3247 · Oct 3, 2022 · Wordfence
medium
Missing Authorization to Authenticated (Subscriber+) Settings Update
Fixed in 6.9.12 · CVE-2022-3622 · Sep 27, 2022 · Wordfence
PHP Object Injection
Fixed in 6.9.4 · Apr 5, 2022 · Wordfence
medium
Reflected Cross-Site Scripting
Fixed in 6.8.7 · CVE-2021-24956 · Nov 22, 2021 · Wordfence
Authenticated SQL Injection (SQLi) vulnerability
Fixed in 6.3.1 · Jun 9, 2020 · Patchstack
high
Authenticated SQL Injection
Fixed in 6.3.1 · CVE-2021-24137 · May 29, 2020 · Wordfence
medium
Reflected Cross-Site Scripting via b2s_id Parameter
Fixed in 5.9.0 · CVE-2019-17550 · Nov 13, 2019 · Wordfence
SQL Injection (SQLi) vulnerability
Fixed in 5.6.0 · Jul 26, 2019 · Patchstack
critical
SQL Injection
Fixed in 5.6.0 · CVE-2019-13572 · Jul 25, 2019 · Wordfence
medium
Reflected Cross-Site Scripting
Fixed in 5.0.3 · CVE-2019-9576 · Mar 5, 2019 · Wordfence
PHP Object Injection
Fixed in 5.0.1 · Sep 21, 2018 · Wordfence
PHP Obj Injection
Fixed in 5.0.1 · WPScan

Questions about Blog2Social’s security

Is Blog2Social safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Blog2Social updated: most attacks target sites that haven’t updated.

Does Blog2Social have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 34 older issues, fixed in earlier versions, so keep Blog2Social up to date.

Is Blog2Social still maintained?

Yes. Its last release was 2 days ago. Its authors resolved 1 of the 1 support threads opened in the last two months.

Is Blog2Social compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.