dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-13431

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-11
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 SlimStat Analytics plugin for WordPress is vulnerable to time-based SQL Injection via the ‘args’ parameter in all versions up to, and including, 5.3.1 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

SQL injection vulnerability in SlimStat Analytics WordPress plugin (versions up to 5.3.1) via the 'args' parameter. Authenticated attackers with Subscriber-level access can inject malicious SQL queries due to insufficient input sanitization and missing prepared statements in the SQL query logic.

MitigationUpdate to the patched version of SlimStat Analytics when available; until then, consider deploying a WAF rule to block SQL injection attempts targeting the 'args' parameter and restrict subscriber-level user permissions if possible.

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 SlimStat Analytics plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'SlimStat Analytics' or check the plugin files in /wp-content/plugins/slimstat/ for version information in the main PHP file header
    Affected if Plugin is installed and version is 5.3.1 or lower
  2. Determine installed plugin version
    Check the version declared in the plugin's main file (usually slimstat.php) or view the plugin details in WordPress admin Plugins page
    Affected if Version is 5.3.1 or any version below this release
  3. Confirm subscriber-level users exist
    Navigate to Users > All Users in WordPress admin and review user roles; or query the wp_usermeta table for users with wp_capabilities containing 'subscriber'
    Affected if Any user account with Subscriber role exists in the WordPress installation
  4. Check if SlimStat feature is accessible to subscribers
    Attempt to access the SlimStat Analytics dashboard or trace functionality while logged in as a Subscriber-level user; examine if the 'args' parameter is accepted via GET or POST requests to the plugin's AJAX endpoints
    Affected if Subscribers can access SlimStat features and the 'args' parameter is processed by the plugin

You are affected if SlimStat Analytics plugin version 5.3.1 or lower is installed AND subscriber-level user accounts exist with access to the plugin's functionality that processes the 'args' parameter.

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 to the patched version of SlimStat Analytics when available; until then, consider deploying a WAF rule to block SQL injection attempts targeting the 'args' parameter and restrict subscriber-level user permissions if possible.

Recommended fix Moderate confidence

Version 5.3.2 or later (check WordPress plugin repository for latest release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate SlimStat Analytics in the plugin list
  4. Check if an update is available for the plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. If no update appears, manually download the latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin is running on a version newer than 5.3.1

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13431 — 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-13431 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