Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-5673 Overview
CVE-2025-5673 is a SQL Injection vulnerability in the Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress. The flaw affects all plugin versions up to and including 8.4.4. It stems from insufficient escaping of the prgSortPostType parameter and lack of proper preparation of the underlying SQL query. Authenticated users with Subscriber-level access or above can append SQL clauses to the existing query and extract sensitive data from the WordPress database. The weakness is classified as CWE-89: Improper Neutralization of Special Elements used in an SQL Command.
Critical Impact
Authenticated attackers holding Subscriber-level accounts or higher can extract arbitrary database contents, including user credentials, session tokens, and private post data.
Affected Products
- Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress
- All versions up to and including 8.4.4
- Vulnerable code path: includes/PRG/Post/Item.php
Discovery Timeline
- 2025-06-17 - CVE-2025-5673 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-5673
Vulnerability Analysis
The vulnerability resides in the Blog2Social plugin's post sorting logic within includes/PRG/Post/Item.php. User-supplied input from the prgSortPostType parameter is concatenated into a SQL query without proper escaping or use of parameterized statements. WordPress exposes the plugin's endpoint to any authenticated session, so attackers only need a Subscriber account, the lowest privileged role in WordPress. Exploitation enables data exfiltration from the wp_users, wp_usermeta, and wp_options tables, exposing password hashes, API keys, and site secrets. The confidentiality impact is high while integrity and availability are not directly affected, consistent with a read-oriented SQL injection.
Root Cause
The plugin builds a dynamic ORDER BY or filter clause using the prgSortPostType request parameter and passes the resulting string to the WordPress database layer without $wpdb->prepare() or an allowlist check. Because wpdb::prepare() cannot parameterize column or table identifiers, the developer must enforce an explicit allowlist of accepted values. The absence of that control allows arbitrary SQL fragments to reach the executor.
Attack Vector
An authenticated attacker sends an HTTP request to the vulnerable plugin endpoint with a malicious prgSortPostType value containing a UNION-based or stacked query payload. The injected clause runs within the context of the WordPress database user, returning query results through the application response or inferable through blind techniques. No user interaction is required beyond holding valid credentials.
Technical references:
Detection Methods for CVE-2025-5673
Indicators of Compromise
- HTTP requests containing the prgSortPostType parameter with SQL syntax such as UNION, SELECT, SLEEP(, --, or /* comments.
- Unexpected authenticated sessions from Subscriber accounts issuing requests to Blog2Social endpoints under /wp-admin/admin.php or /wp-admin/admin-ajax.php.
- Database error messages referencing prgSortPostType or malformed ORDER BY clauses in PHP error logs.
- New or unfamiliar Subscriber-role accounts created shortly before suspicious plugin requests.
Detection Strategies
- Deploy a Web Application Firewall rule that inspects the prgSortPostType parameter and blocks values that do not match an allowlist of expected post type slugs.
- Enable MySQL general query logging on test systems to confirm malicious queries, then correlate against web access logs in production.
- Review authenticated request patterns for Subscriber accounts, which should rarely interact with plugin administrative endpoints.
Monitoring Recommendations
- Forward WordPress access logs, PHP error logs, and database logs to a centralized analytics platform for correlation.
- Alert on repeated 500 responses or long-running queries originating from Blog2Social endpoints.
- Track creation of new WordPress users and privilege changes in near real time.
How to Mitigate CVE-2025-5673
Immediate Actions Required
- Update the Blog2Social plugin to a release later than 8.4.4 that remediates the prgSortPostType injection.
- Audit the WordPress user table and remove unknown Subscriber or higher accounts.
- Rotate WordPress administrator passwords, API keys stored in wp_options, and any secrets that may have been exfiltrated.
- Review database query logs for signs of exploitation during the exposure window.
Patch Information
The vendor must release a fixed version of Blog2Social that validates prgSortPostType against an allowlist and uses $wpdb->prepare() with proper placeholders. Site administrators should install the latest available version through the WordPress plugin repository. Consult the Wordfence Vulnerability Report for the current fixed version.
Workarounds
- Deactivate and remove the Blog2Social plugin until the patched version can be installed.
- Restrict user registration to disable Subscriber-level self-service accounts on affected sites.
- Configure a WAF rule to drop requests where prgSortPostType contains characters outside [A-Za-z0-9_-].
- Enforce least privilege on the WordPress database user, limiting it to the specific site database only.
# Example ModSecurity rule to block SQL metacharacters in prgSortPostType
SecRule ARGS:prgSortPostType "@rx [^A-Za-z0-9_\-]" \
"id:1005673,phase:2,deny,status:403,\
msg:'CVE-2025-5673 Blog2Social SQLi attempt',\
tag:'cwe/89',log"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

