vciy

CVE-2021-24750

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

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

CVE-2021-247504 of 4 sources documented this
47

rank 47 = 21 + 22 + 2 + 2 + 0

rank@v1 · this cycle

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.38298  ·  without this subject the record ranks 26

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.8, from NVD  ·  without this subject the record ranks 25

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-10-09  ·  without this subject the record ranks 45

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 45

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 47

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.91Mover the next 30 days, if this record is yours
Movement+$3.08Mon 2024-12-17, the last material move, 1 year, 6 months before this reading
Basisassumeda published average, not your estate

$1.91M = $4.99M incident cost x 1 exposure x 0.38298 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.38298EPSSNOT IN KEVas of 2026-09-20
Severity8.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementrisenreceipt
RISING10Risen from 0.00624 to 0.38298 across 45 observations. arc-rules@v1

Foresight · where to check next

CVE-2023-34362CVE-2021-42258CVE-2020-29574CVE-2017-18362FortinetProgress Software24750

This record is one instance of CWE-89, improper neutralization of special elements used in an sql command ('sql injection'). The index holds 20889 prior instances of this class, 31 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running WP Visitor Statistics (Real Time Traffic)? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')receipt
Published consequencesCWE-89: Confidentiality, Integrity, Availability: Execute Unauthorized Code or Commands; Confidentiality: Read Application Data; Authentication: Gain Privileges or Assume Identity, Bypass Protection…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in4.8receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2022-01-14.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2022-01-14receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD8.8 HIGHreceipt
Exploit probability0.38298 · top 2% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byWPScanreceipt
Recorded changes48 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productWP Visitor Statistics (Real Time Traffic)receipt
Published rangescodepress visitor statistics < 4.8receipt
Fixed in4.8receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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 receipt

NVD's analysis a second authority

severity
8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-89
affected versions
codepress visitor statistics < 4.8

check it yourself wpscan.com plugins.trac.wordpress.org packetstormsecurity.com receipt

Dated events

2022-02-04EPSS moved 0.04 to 0.132024-12-17EPSS moved 0.05 to 0.672026-06-15EPSS moved 0.64 to 0.35

Movement the material steps

22 Dec 20210.00624
4 Feb 20220.13355 · crossed 0.10
7 Mar 20230.00562 · crossed 0.10 · scoring model v2023.03.01
17 Dec 20240.66673 · crossed 0.10 and 0.50
17 Mar 20250.7296 · scoring model v2025.03.14
24 Mar 20250.59612
29 Mar 20250.70349
15 Aug 20250.576
9 Oct 20250.71494
18 Nov 20250.57553
21 Nov 20250.71494
15 Jun 20260.35227 · crossed 0.50 · scoring model v2026.06.15
26 Jun 20260.38298
Show all 45 observations
22 Dec 20210.00624
6 Jan 20220.0363
4 Feb 20220.13355
15 Jul 20220.20994
15 Nov 20220.13355
7 Mar 20230.00562
3 Jun 20230.00533
14 Jul 20230.00776
29 Jul 20230.00793
12 Aug 20230.00791
20 Nov 20230.00964
6 Dec 20230.01207
17 Jan 20240.02112
31 Jan 20240.01467
28 Feb 20240.01462
11 Apr 20240.01945
8 May 20240.02059
4 Jun 20240.02891
12 Nov 20240.03490
26 Nov 20240.04861
17 Dec 20240.66673
24 Dec 20240.67361
23 Jan 20250.67373
17 Mar 20250.7296
19 Mar 20250.78321
20 Mar 20250.7296
23 Mar 20250.67398
24 Mar 20250.59612
26 Mar 20250.67398
29 Mar 20250.70349
30 Mar 20250.67398
23 Apr 20250.64801
1 Jun 20250.67615
25 Jul 20250.72314
15 Aug 20250.576
9 Oct 20250.71494
18 Nov 20250.57553
21 Nov 20250.71494
16 Dec 20250.69584
19 Jan 20260.71527
3 Feb 20260.69507
15 May 20260.64331
15 Jun 20260.35227
21 Jun 20260.38555
26 Jun 20260.38298

45 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.38298Published2021-12-21Public PoC2022-01-14Index as of2026-06-26

The record had been public for 4 years, 6 months when this index was last written.

Published 2021-12-21 receipt · Public PoC 2022-01-14 receipt · Index as of 2026-06-26 derived

The pattern, elsewhere

This record is one instance of CWE-89, improper neutralization of special elements used in an sql command ('sql injection'). The index holds 20889 prior instances of this class, 31 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2023-34362matches 7 of 8KEV listed · 2023receipt
CVE-2021-42258matches 7 of 8KEV listed · 2021receipt
CVE-2020-29574matches 7 of 8KEV listed · 2020receipt
CVE-2017-18362matches 7 of 8KEV listed · 2019receipt
CVE-2023-48788 · Fortinet FortiClientEMSmatches 7 of 9KEV listed · 2024receipt
CVE-2024-6670 · Progress Software Corporation WhatsUp Goldmatches 7 of 9KEV listed · 2024receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

20889 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

unknown wp visitor statistics (real time traffic)

Of the 3 records in this family, this is the only one holding a stated fix version: 4.8.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2021-24750.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.