dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-5673

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to SQL Injection via the ‘prgSortPostType’ parameter in all versions up to, and including, 8.4.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Blog2Social WordPress plugin fails to properly sanitize the 'prgSortPostType' parameter before using it in a SQL query. An authenticated attacker with subscriber-level access can inject arbitrary SQL commands via this parameter to extract sensitive data from the database.

MitigationUpdate the Blog2Social plugin to a version beyond 8.4.4 once the patch is released, or apply a WAF rule to block SQL injection attempts targeting the prgSortPostType parameter until an update is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Blog2Social plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for Blog2Social, or inspect the file /wp-content/plugins/blog2social/ folder exists
    Affected if Blog2Social plugin is present in the WordPress installation
  2. Check installed Blog2Social version
    In WordPress admin, view the Plugins list and note the version number displayed under Blog2Social, or check the main plugin file header in /wp-content/plugins/blog2social/includes/ or blog2social.php for the 'Version' comment
    Affected if Installed version is 8.4.4 or earlier
  3. Confirm access to the vulnerable parameter
    Identify if the WordPress site allows subscriber-level users (or higher) to access the admin dashboard or any frontend area where Blog2Social features are exposed; check user role capabilities for the 'prgSortPostType' parameter usage in Blog2Social functionality
    Affected if The site has user accounts with subscriber-level access or higher that can trigger Blog2Social features
  4. Inspect HTTP requests for prgSortPostType parameter
    If you have access to server logs or traffic monitoring, review requests to Blog2Social endpoints (typically admin-ajax.php or blog2social-related AJAX calls) for the 'prgSortPostType' parameter being passed
    Affected if The parameter is being used in requests without proper sanitization logic present in the plugin code

A user is affected if Blog2Social plugin version 8.4.4 or earlier is installed and the prgSortPostType parameter is accessible to authenticated users (subscriber-level or higher).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Blog2Social plugin to a version beyond 8.4.4 once the patch is released, or apply a WAF rule to block SQL injection attempts targeting the prgSortPostType parameter until an update is available.

Recommended fix High confidence

Upgrade to Blog2Social version 8.4.5 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Blog2Social: Social Media Auto Post & Scheduler
  4. Check if current version is 8.4.4 or earlier
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/blog2social/ and upload manually
  7. After update, verify the plugin version is 8.4.5 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5673 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5673 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data