# CVE-2021-24750: WP Visitor Statistics (Real Time Traffic) < 4.8 - Subscriber+ SQL Injection

> Authenticated subscribers can perform SQL injection via the refUrl parameter in the WP Visitor Statistics plugin, potentially exposing or modifying database content.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p934-c89c-rc2m

## What is CVE-2021-24750?

CVE-2021-24750 is a high-severity SQL injection vulnerability in Unknown WP Visitor Statistics (Real Time Traffic), published on 21 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 4.8 does not properly sanitise and escape the refUrl in the refDetails AJAX action, available to any authenticated user, which could allow users with a role as low as subscriber to perform SQL injection attacks

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2021-24750?

It affects 1 product.


Products: Codepress Visitor Statistics.

## How do I fix CVE-2021-24750?

No fix has been published for CVE-2021-24750 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-24750 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24750 exists.

Public exploit code:

- Demonstration of the WP Visitor Statistics plugin exploit (github_poc): https://github.com/fimtow/CVE-2021-24750
- WordPress Plugin WP Visitor Statistics 4.7 - SQL Injection (exploitdb)
- WordPress Visitor Statistics (Real Time Traffic) <4.8 -SQL Injection (nuclei): http/cves/2021/CVE-2021-24750.yaml

## Other vulnerabilities in Unknown WP Visitor Statistics (Real Time Traffic)

- [CVE-2023-0600](https://insights.sbomify.com/CVE-2023-0600/): WP Visitor Statistics (Real Time Traffic) < 6.9 - Unauthenticated SQLi (critical 9.8)
- [CVE-2022-33965](https://insights.sbomify.com/CVE-2022-33965/): WordPress WP Visitor Statistics plugin <= 5.7 - Multiple Unauthenticated SQL Injection (SQLi) vulnerabilities (critical 9.3)
- [CVE-2022-0410](https://insights.sbomify.com/CVE-2022-0410/): WP Visitor Statistics (Real Time Traffic) < 5.6 - Subscriber+ SQL Injection (high 8.8)
- [CVE-2022-4656](https://insights.sbomify.com/CVE-2022-4656/): WP Visitor Statistics (Real Time Traffic) < 6.5 - Contributor+ Stored XSS via Shortcode (medium 5.4)
- [CVE-2021-25042](https://insights.sbomify.com/CVE-2021-25042/): WP Visitor Statistics (Real Time Traffic) < 5.5 - Arbitrary IP Address Exclusion to Stored XSS (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24750 and fix it if it is affected.

What it is: CVE-2021-24750 is a high-severity SQL injection vulnerability in Unknown WP Visitor Statistics (Real Time Traffic), published on 21 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24750 exists.

Affected product: Unknown WP Visitor Statistics (Real Time Traffic). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-24750/ (Markdown: https://insights.sbomify.com/CVE-2021-24750/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-24750
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-24750
- OSV: https://osv.dev/vulnerability/CVE-2021-24750

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-24750/
Summaries are generated and may contain mistakes; the official description above is the record.