CVE-2022-25149

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 77% (99th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2022-29892 (ENISA EUVD) · GHSA-gmjf-vvgp-p553 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 77%
CISA-KEV: Not listedEPSS PROB: 77%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

Update to version 13.1.6 or newer (from the CVE record's solution, Wordfence) — apply it.

The WP Statistics WordPress plugin is vulnerable to SQL Injection due to insufficient escaping and parameterization of the IP parameter found in the ~/includes/class-wp-statistics-hits.php file which allows attackers without authentication to inject arbitrary SQL queries to obtain sensitive information, in versions up to and including 13.1.5.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
90
EG Risk 90/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation77% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Update to version 13.1.6 or newer (from the CVE record's solution, Wordfence). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
77%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
77% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

Update to version 13.1.6 or newer (from the CVE record's solution, Wordfence). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 24, 2022

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Oct 11, 2026
Fix named in the CVE record's solution (Wordfence).
Web page

WordPress Plugin WP Statistics <= 13.1.5 - Multiple Unauthenticated SQL Injection vulnerabilities · GitHub

https://gist.github.com/Xib3rR4dAr/5dbd58b7f57a5037fe461fba8e696042

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 185 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 85 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 07:07 UTCEchelonGraph re-scored
  2. 2026-11-13 07:07 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  3. 2026-11-12 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  4. 2026-11-12 06:07 UTCEchelonGraph re-scored
  5. 2026-11-12 06:07 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  6. 2026-11-11 16:32 UTCEPSS rescoreEPSS 77% · 99th percentile
  7. 2026-11-11 05:08 UTCEchelonGraph re-scored
  8. 2026-11-11 05:08 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  9. 2026-11-10 04:11 UTCEchelonGraph re-scored
  10. 2026-11-10 04:11 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  11. 2026-11-09 03:09 UTCEchelonGraph re-scored
  12. 2026-11-09 03:09 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  13. 2026-11-08 16:33 UTCEPSS rescoreEPSS 77% · 99th percentile
  14. 2026-11-08 02:12 UTCEchelonGraph re-scored
  15. 2026-11-08 02:12 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  16. 2026-11-07 01:08 UTCEchelonGraph re-scored
  17. 2026-11-07 01:08 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  18. 2026-11-06 16:30 UTCEPSS rescoreEPSS 77% · 99th percentile
  19. 2026-11-06 00:07 UTCEchelonGraph re-scored
  20. 2026-11-06 00:07 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  21. 2026-11-05 16:31 UTCEPSS rescoreEPSS 77% · 99th percentile
  22. 2026-11-04 23:10 UTCEchelonGraph re-scored
  23. 2026-11-04 23:10 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  24. 2026-11-04 16:30 UTCEPSS rescoreEPSS 77% · 99th percentile
  25. 2026-11-03 22:12 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-03 22:12 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  2. 2026-11-02 21:09 UTCEchelonGraph re-scored
  3. 2026-11-02 21:09 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  4. 2026-11-01 20:12 UTCEchelonGraph re-scored
  5. 2026-11-01 20:12 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  6. 2026-10-31 19:15 UTCEchelonGraph re-scored
  7. 2026-10-31 19:15 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  8. 2026-10-31 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  9. 2026-10-30 18:17 UTCEchelonGraph re-scored
  10. 2026-10-30 18:17 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  11. 2026-10-29 17:21 UTCEchelonGraph re-scored
  12. 2026-10-29 17:21 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  13. 2026-10-29 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  14. 2026-10-28 16:23 UTCEchelonGraph re-scored
  15. 2026-10-28 16:23 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  16. 2026-10-27 16:28 UTCEPSS rescoreEPSS 77% · 99th percentile
  17. 2026-10-27 15:26 UTCEchelonGraph re-scored
  18. 2026-10-27 15:26 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  19. 2026-10-26 16:28 UTCEPSS rescoreEPSS 77% · 99th percentile
  20. 2026-10-26 14:07 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  21. 2026-10-25 18:12 UTCEchelonGraph re-scored
  22. 2026-10-25 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  23. 2026-10-25 12:42 UTCEchelonGraph re-scored
  24. 2026-10-25 12:42 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  25. 2026-10-24 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  26. 2026-10-24 11:44 UTCEchelonGraph re-scored
  27. 2026-10-24 11:44 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  28. 2026-10-23 10:47 UTCEchelonGraph re-scored
  29. 2026-10-23 10:47 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  30. 2026-10-22 09:49 UTCEchelonGraph re-scored
  31. 2026-10-22 09:48 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  32. 2026-10-21 16:28 UTCEPSS rescoreEPSS 77% · 99th percentile
  33. 2026-10-21 08:50 UTCEchelonGraph re-scored
  34. 2026-10-21 08:49 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  35. 2026-10-20 07:52 UTCEchelonGraph re-scored
  36. 2026-10-20 07:52 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  37. 2026-10-19 16:28 UTCEPSS rescoreEPSS 77% · 99th percentile
  38. 2026-10-19 06:55 UTCEchelonGraph re-scored
  39. 2026-10-19 06:55 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  40. 2026-10-18 05:57 UTCEchelonGraph re-scored
  41. 2026-10-18 05:56 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  42. 2026-10-17 04:58 UTCEchelonGraph re-scored
  43. 2026-10-17 04:58 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  44. 2026-10-16 16:34 UTCEPSS rescoreEPSS 77% · 99th percentile
  45. 2026-10-16 03:59 UTCEchelonGraph re-scored
  46. 2026-10-16 03:59 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  47. 2026-10-15 00:58 UTCEchelonGraph re-scored
  48. 2026-10-15 00:57 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  49. 2026-10-14 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  50. 2026-10-13 22:12 UTCEchelonGraph re-scored
  51. 2026-10-13 22:11 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  52. 2026-10-13 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  53. 2026-10-12 18:54 UTCEchelonGraph re-scored
  54. 2026-10-12 18:54 UTCGHSA enrichmentGHSA-gmjf-vvgp-p553 · GitHub severity HIGH
  55. 2026-10-11 23:24 UTCEchelonGraph re-scored
  56. 2026-10-10 19:56 UTCEPSS rescoreEPSS 77% · 99th percentile
  57. 2026-10-09 20:04 UTCEPSS rescoreEPSS 77% · 99th percentile
  58. 2026-10-07 23:45 UTCEPSS rescoreEPSS 77% · 99th percentile
  59. 2026-10-06 15:14 UTCEPSS rescoreEPSS 77% · 99th percentile
  60. 2026-09-30 15:51 UTCEchelonGraph re-scored
  61. 2026-09-30 15:00 UTCEPSS rescoreEPSS 77% · 99th percentile
  62. 2026-09-28 13:48 UTCEPSS rescoreEPSS 77% · 99th percentile
  63. 2026-09-27 13:41 UTCEPSS rescoreEPSS 77% · 99th percentile
  64. 2026-09-24 14:00 UTCEPSS rescoreEPSS 77% · 99th percentile
  65. 2026-09-23 13:45 UTCEPSS rescoreEPSS 77% · 99th percentile
  66. 2026-09-17 19:23 UTCEPSS rescoreEPSS 77% · 99th percentile
  67. 2026-09-16 14:05 UTCEPSS rescoreEPSS 77% · 99th percentile
  68. 2026-09-15 03:06 UTCEPSS rescoreEPSS 77% · 99th percentile
  69. 2026-09-12 14:57 UTCEPSS rescoreEPSS 77% · 99th percentile
  70. 2026-09-11 14:49 UTCEPSS rescoreEPSS 77% · 99th percentile
  71. 2026-09-06 13:45 UTCEPSS rescoreEPSS 77% · 99th percentile
  72. 2026-09-05 15:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  73. 2026-09-04 13:57 UTCEPSS rescoreEPSS 78% · 99th percentile
  74. 2026-09-02 14:09 UTCEPSS rescoreEPSS 78% · 99th percentile
  75. 2026-08-30 19:14 UTCEPSS rescoreEPSS 78% · 99th percentile

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2022/CVE-2022-25149.yaml
    Published Oct 17, 2023

    WordPress Plugin WP Statistics <= 13.1.5 - SQL Injection

    Open source ↗

Frequently asked(5)

What is CVE-2022-25149?
CVE-2022-25149 is a critical-severity vulnerability; its CVE record was published on February 24, 2022. The WP Statistics WordPress plugin is vulnerable to SQL Injection due to insufficient escaping and parameterization of the IP parameter found in the ~/includes/class-wp-statistics-hits.php file which allows attackers without authentication to inject arbitrary SQL queries to obtain sensitive…
When was the CVE record for CVE-2022-25149 published?
The CVE record for CVE-2022-25149 was published on February 24, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-25149 actively exploited?
CVE-2022-25149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 77% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-25149?
CVE-2022-25149 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-25149?
The CVE record's solution for CVE-2022-25149, written by its CNA Wordfence, names the fix: "Update to version 13.1.6 or newer."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-25149

Explore →

Is Your Infrastructure Affected by CVE-2022-25149?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.