Skip to content
Laskyr

Plugins · social-web-suite · data as of 2026-11-04

Is Social Web Suite safe? Known vulnerabilities and latest version

Social Web Suite is closed on wordpress.org

Closed on 2026-09-28. Closed plugins get no updates through WordPress, so new security holes will not be fixed for you.

Status
Closed 2026-09-28
Known issues on record
4
Unpatched in latest
0

What to do

  1. Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
  2. Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
  3. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate social-web-suite && wp plugin delete social-web-suite

Check your version

Known vulnerabilities

4 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 4 record(s) do not state which versions are affected.

high 7.5 CVE-2026-93904 · published 2026-10-29

SQL injection in Social Web Suite (4.1.12 and older)

Affected
4.1.12 and older
Fixed in
unknown
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Social Web Suite – Social Media Auto Post, Social Media Auto Publish plugin for WordPress is vulnerable to generic SQL Injection via the 'exclude_posts' parameter in all versions up to, and including, 4.1.12 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The HMAC authentication gate protecting the endpoint is bypassable on any freshly activated installation where an administrator has not yet visited the settings page, because the secret_key option remains empty until lazily generated at that point, allowing an attacker to compute a valid token using hash_hmac('sha256', '', $timestamp) with any chosen timestamp.

NVD CVE-2026-93904Wordfence advisoryPlugin source

high 8.6 CVE-2026-88930 · published 2026-10-11

SQL injection in Social Web Suite (4.1.12 and older)

Affected
4.1.12 and older
Fixed in
unknown
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory

The Social Web Suite WordPress plugin through 4.1.12 does not require its shared secret to be set before accepting requests authorised by it, and does not sanitise and escape a parameter before using it in an SQL statement, allowing unauthenticated users to perform SQL injection attacks.

NVD CVE-2026-88930WPScan advisory

medium 5.3 CVE-2026-88931 · published 2026-10-09

Missing authorization check in Social Web Suite (4.1.12 and older)

Affected
4.1.12 and older
Fixed in
unknown
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory

The Social Web Suite WordPress plugin through 4.1.12 does not restrict which of its settings may be written through an unauthenticated endpoint, allowing attackers to overwrite arbitrary Social Web Suite WordPress plugin through 4.1.12 options, including the shared secret that guards its own privileged endpoints.

NVD CVE-2026-88931WPScan advisory

high 7.5 CVE-2024-8352 · published 2024-10-03

Path traversal / file read in Social Web Suite (4.1.11 and older)

Affected
4.1.11 and older
Fixed in
unknown
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Social Web Suite – Social Media Auto Post, Social Media Auto Publish plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.1.11 via the download_log function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.

NVD CVE-2024-8352Wordfence advisoryCode change (fix)Plugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Social Web Suite vulnerability status badge
<a href="https://laskyr.com/plugins/social-web-suite"><img src="https://laskyr.com/plugins/social-web-suite/badge.svg" alt="Social Web Suite vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit