CVE-2024-13321: The AnalyticsWP plugin for WordPress is vulnerable to SQL Injection via the 'custom_sql' parameter in all vers

Q: How do I fix CVE-2024-13321?

analyticswp: upgrade to 2.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-13321 being exploited?

CVE-2024-13321 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-13321 affect?

CVE-2024-13321 affects analyticswp. Severity is high (CVSS 7.5). 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 possi

Q: How urgent is CVE-2024-13321?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2024-13321 is a high-severity flaw (CVSS 7.5) affecting analyticswp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-89
Published	2025-03-14
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: analyticswp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-14 08:15 UTCPublished CVE record published
2026-06-17 07:01 UTCUpdated Record last modified

analyticswp analyticswp UPGRADE

Affected: < 2.1.0

Fixed in: 2.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy analyticswp || rpm -q analyticswp || analyticswp --version

2. UPGRADE to 2.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade analyticswp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade analyticswp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-13321?

analyticswp: upgrade to 2.1.0. Exact commands for each OS are on this page.

Is CVE-2024-13321 being exploited?

CVE-2024-13321 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-13321 affect?

CVE-2024-13321 affects analyticswp. Severity is high (CVSS 7.5). 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 possi

How urgent is CVE-2024-13321?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs