Blog2Social: Social Media Auto Post & Scheduler: known security problems
30 known security problems reported for this WordPress plugin, with the affected versions, the fix and what to do.
Updated
In short
There are 30 known security problems on this page. Each one has a fixed version. Updating to version 9.1.5 or newer covers every fixed problem listed here.
Based on public reports. Check the plugin’s changelog. Watchfox AI may be wrong.
Get an email when your site is affected: install Watchfox AI (free)
Someone with a contributor account on your site could see private information they should not see
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 9.1.4
- Fixed in
- 9.1.5
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 9.1.5 or newer.
- Official ID
- CVE-2026-108092
- Report title
- Social Media Auto Post & Scheduler <= 9.1.4 - Authenticated (Contributor+) Insecure Direct Object Reference to Sensitive Information Exposure
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could do things on your site they should not be allowed to
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 9.1.0
- Fixed in
- 9.1.1
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 9.1.1 or newer.
- Official ID
- CVE-2026-92829
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 9.1.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Modification via Multiple AJAX Handlers
- First reported
- Sources
- Wordfence, seen
Someone could use it to harm your site (up to and including 9.0.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 9.0.0
- Fixed in
- 9.1.0
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 9.1.0 or newer.
- Official ID
- CVE-2026-89031
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 9.0.0 - Insecure Direct Object Reference
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could use it to harm your site (up to and including 9.0.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 9.0.0
- Fixed in
- 9.1.0
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 9.1.0 or newer.
- Official ID
- CVE-2026-89029
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 9.0.0 - Authenticated (Subscriber+) Username Enumeration
- First reported
- Sources
- Wordfence, seen
Someone could do things on your site they should not be allowed to
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 9.0.0
- Fixed in
- 9.1.0
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 9.1.0 or newer.
- Official ID
- CVE-2026-89030
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 9.0.0 - Missing Authorization
- First reported
- Sources
- Wordfence, seen
A stranger could plant harmful code that runs for your visitors or admins
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.9.2
- Fixed in
- 8.9.3
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.9.3 or newer.
- Official ID
- CVE-2026-56044
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.9.2 - Unauthenticated Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could do things on your site they should not be allowed to (up to and including 8.9.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.9.0
- Fixed in
- 8.9.1
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.9.1 or newer.
- Official ID
- CVE-2026-7051
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.9.0 - Missing Authorization to Authenticated (Subscriber+) Delete Arbitrary B2S Post Records via 'postId' Parameter
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could use it to harm your site (up to and including 8.8.3)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.8.3
- Fixed in
- 8.8.4
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.8.4 or newer.
- Official ID
- CVE-2026-4330
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.8.3 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Post Schedule Modification via 'b2s_id' Parameter
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could do things on your site they should not be allowed to (up to and including 8.8.2)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.8.2
- Fixed in
- 8.8.3
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.8.3 or newer.
- Official ID
- CVE-2026-4331
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.8.2 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Meta Deletion via 'b2s_reset_social_meta_tags' AJAX Action
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could do things on your site they should not be allowed to (up to and including 8.7.4)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.7.4
- Fixed in
- 8.7.5
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.7.5 or newer.
- Official ID
- CVE-2026-1942
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.7.4 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Modification
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could see private information they should not see
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.7.2
- Fixed in
- 8.7.3
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.7.3 or newer.
- Official ID
- CVE-2025-14943
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.7.2 - Incorrect Authorization to Authenticated (Subscriber+) Sensitive Information Exposure
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could do things on your site they should not be allowed to (up to and including 8.7.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.7.0
- Fixed in
- 8.7.1
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.7.1 or newer.
- Official ID
- CVE-2025-13558
- Report title
- Blog2Social <= 8.7.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Trashing
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could make your server visit other addresses on their behalf (up to and including 8.6.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.6.0
- Fixed in
- 8.6.1
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.6.1 or newer.
- Official ID
- CVE-2025-12560
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.6.0 - Authenticated (Subscriber+) Blind Server-Side Request Forgery via post_url
- First reported
- Sources
- Wordfence, seen
Someone could use it to harm your site (up to and including 8.6.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.6.0
- Fixed in
- 8.6.1
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.6.1 or newer.
- Official ID
- CVE-2025-12563
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.6.0 - Incorrect Authorization to Video File Upload
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could read or change the data in your site’s database (up to and including 8.4.4)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.4.4
- Fixed in
- 8.4.5
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.4.5 or newer.
- Official ID
- CVE-2025-5673
- Report title
- Blog2Social <= 8.4.4 - Authenticated (Subscriber+) SQL Injection via `prgSortPostType` Parameter
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 8.3.3
- Fixed in
- 8.4.0
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 8.4.0 or newer.
- Official ID
- CVE-2025-4133
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 8.3.3 - Authenticated (Contributor+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone with an author account on your site could plant harmful code that runs for your visitors or admins
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 7.5.4
- Fixed in
- 7.5.5
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 7.5.5 or newer.
- Official ID
- CVE-2024-7302
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 7.5.4 - Authenticated (Author+) Stored Cross-Site Scripting via File Upload
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could read or change the data in your site’s database (up to and including 7.4.1)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 7.4.1
- Fixed in
- 7.4.2
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 7.4.2 or newer.
- Official ID
- CVE-2024-3549
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 7.4.1 - Authenticated (Subscriber+) SQL Injection
- First reported
- Sources
- Wordfence, seen
Someone could use it to harm your site (up to and including 7.4.2)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 7.4.2
- Fixed in
- 7.5.0
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 7.5.0 or newer.
- Official ID
- CVE-2024-3678
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 7.4.2 - Information Exposure
- First reported
- Sources
- Wordfence, seen
Someone could plant harmful code that runs for your visitors or admins (before 7.2.1)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Before 7.2.1
- Fixed in
- 7.2.1
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 7.2.1 or newer.
- Official ID
- CVE-2023-3936
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 7.2.0 - Reflected Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could make your server visit other addresses on their behalf (up to and including 6.9.9)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 6.9.9
- Fixed in
- 6.9.10
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 6.9.10 or newer.
- Official ID
- CVE-2022-3247
- Report title
- Blog2Social <= 6.9.9 - Authenticated (Subscriber+) Server-Side Request Forgery
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could read or change the data in your site’s database (up to and including 6.9.9)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 6.9.9
- Fixed in
- 6.9.10
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 6.9.10 or newer.
- Official ID
- CVE-2022-3246
- Report title
- Blog2Social <= 6.9.9 - Authenticated (Subscriber+) SQL Injection
- First reported
- Sources
- Wordfence, seen
Anyone with an account on your site, even a basic one could do things on your site they should not be allowed to (up to and including 6.9.11)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 6.9.11
- Fixed in
- 6.9.12
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 6.9.12 or newer.
- Official ID
- CVE-2022-3622
- Report title
- Blog2Social <= 6.9.11 - Missing Authorization to Authenticated (Subscriber+) Settings Update
- First reported
- Sources
- Wordfence, seen
Someone could in some setups, take over your site (up to and including 6.9.3)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 6.9.3
- Fixed in
- 6.9.4
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 6.9.4 or newer.
- Report title
- Blog2Social <= 6.9.3 - PHP Object Injection
- First reported
- Sources
- Wordfence, seen
Someone could plant harmful code that runs for your visitors or admins (up to and including 6.8.6)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 6.8.6
- Fixed in
- 6.8.7
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 6.8.7 or newer.
- Official ID
- CVE-2021-24956
- Report title
- Blog2Social <= 6.8.6 - Reflected Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone could read or change the data in your site’s database (up to and including 6.3.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 6.3.0
- Fixed in
- 6.3.1
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 6.3.1 or newer.
- Official ID
- CVE-2021-24137
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 6.3.0 - Authenticated SQL Injection
- First reported
- Sources
- Wordfence, seen
Someone could plant harmful code that runs for your visitors or admins (before 5.9.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Before 5.9.0
- Fixed in
- 5.9.0
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 5.9.0 or newer.
- Official ID
- CVE-2019-17550
- Report title
- Blog2Social: Social Media Auto Post & Scheduler < 5.9.0 - Reflected Cross-Site Scripting via b2s_id Parameter
- First reported
- Sources
- Wordfence, seen
Someone could read or change the data in your site’s database (before 5.6.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Before 5.6.0
- Fixed in
- 5.6.0
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 5.6.0 or newer.
- Official ID
- CVE-2019-13572
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 5.5.0 - SQL Injection
- First reported
- Sources
- Wordfence, seen
Someone could plant harmful code that runs for your visitors or admins (before 5.0.3)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Before 5.0.3
- Fixed in
- 5.0.3
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 5.0.3 or newer.
- Official ID
- CVE-2019-9576
- Report title
- Blog2Social: Social Media Auto Post & Scheduler <= 5.0.2 - Reflected Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone could in some setups, take over your site (before 5.0.1)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Before 5.0.1
- Fixed in
- 5.0.1
- What to do
- If your site has an affected version, update Blog2Social: Social Media Auto Post & Scheduler to version 5.0.1 or newer.
- Report title
- Blog2Social: Social Media Auto Post & Scheduler < 5.0.1 - PHP Object Injection
- First reported
- Sources
- Wordfence, seen
Where this comes from
We collect these reports from public security sources and rewrite them in plain words. Each problem shows its sources and the date we first saw it. This page never says whether your own site is affected: only a check of your site’s versions can tell.
Get an email when your site is affected.
Install Watchfox AI once. It checks your plugins and themes against this list every day, for free.
Install Watchfox AI (free)