Skip to content
Fencer Intel
high 8.8

CVE-2021-24750 in the critical feed json

WP Visitor Statistics (Real Time Traffic) < 4.8 - Subscriber+ SQL Injection

published 4y ago modified 4mo ago also EUVD-2021-11662

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
38.3%
EPSS 38.3% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

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

Patch / fix

  • codepress visitor_statistics 4.8

Is CVE-2021-24750 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-50619)

Exploit prediction

38.30% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-50619 WordPress Plugin WP Visitor Statistics 4.7 - SQL Injection webapps, 2022-01-05
  • Nuclei template WordPress Visitor Statistics (Real Time Traffic) <4.8 -SQL Injection nuclei detection template
  • wpscan.com https://wpscan.com/vulnerability/7528aded-b8c9-4833-89d6-9cd7df3620de referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/165433/WordPress-WP-Visitor-Statistics-4.7-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

  • Unknown WP Visitor Statistics (Real Time Traffic)

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.