dbcve.org
AnalyticswpWordPress extension

CVE-2024-13321

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 AnalyticsWP plugin for WordPress is vulnerable to SQL Injection via the 'custom_sql' parameter in all versions up to, and including, 2.0.0 due to insufficient authorization checks on the handle_get_stats() function. 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.

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 AnalyticsWP WordPress plugin is vulnerable to SQL injection in the handle_get_stats() function via the 'custom_sql' parameter. Due to insufficient authorization checks, unauthenticated attackers can inject arbitrary SQL queries to extract sensitive data from the database.

MitigationUpdate AnalyticsWP to version 2.0.1 or later. If no update is available, disable the plugin and deploy WAF rules to block SQL injection attempts targeting the custom_sql parameter.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AnalyticswpWordPress extension
Affected:< 2.1.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 AnalyticsWP plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'AnalyticsWP' or 'Analyticswp Analyticswp' in the plugin list
    Affected if The plugin appears in the installed plugins list
  2. Determine installed plugin version
    Click on the plugin name in the WordPress plugins list to view its details, or inspect the plugin header in wp-content/plugins/analyticswp-analyticswp/analyticswp.php for the Version field
    Affected if The version number displayed is less than 2.1.0 (e.g., 2.0.9, 1.x.x, etc.)
  3. Confirm plugin is active
    Check the plugins list status column in WordPress admin - the plugin must be activated for the vulnerability to be exploitable
    Affected if The plugin shows as 'Active' under the status column
  4. Check for unauthenticated access to vulnerable endpoint
    Inspect if the plugin registers any REST API routes or admin-ajax.php endpoints that call handle_get_stats() and accept the custom_sql parameter without authentication checks
    Affected if The plugin exposes an endpoint accessible to unauthenticated users that processes the custom_sql parameter

The environment is affected if AnalyticsWP plugin is installed, active, and running a version prior to 2.1.0, making the unauthenticated SQL injection via the custom_sql parameter exploitable.

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
Upgrade available Upgrade to 2.1.0 or later
Fixed in 2.1.0
Interim mitigation

Update AnalyticsWP to version 2.0.1 or later. If no update is available, disable the plugin and deploy WAF rules to block SQL injection attempts targeting the custom_sql parameter.

Recommended fix High confidence

AnalyticsWP version 2.1.0 or later

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find the AnalyticsWP plugin and click 'Update now' or manually upload version 2.1.0 or later
  4. Verify the plugin version after update to confirm 2.1.0 or higher is installed
  5. Test that the AnalyticsWP functionality works correctly post-update

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

Fix this in Analyticswp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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