CVE-2022-0513

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: 53% (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-15641 (ENISA EUVD) · GHSA-6gr9-x8m9-c46v (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 53%
CISA-KEV: Not listedEPSS PROB: 53%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

Update to version 13.1.5 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 exclusion_reason parameter found in the ~/includes/class-wp-statistics-exclusion.php file which allows attackers without authentication to inject arbitrary SQL queries to obtain sensitive information, in versions up to and including 13.1.4. This requires the "Record Exclusions" option to be enabled on the vulnerable site.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
80
EG Risk 80/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.
Exploitation53% × 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.5 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
53%
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
53% 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.5 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 16, 2022

Last Modified

November 21, 2024

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 55× 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 236 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 136 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-0513?
CVE-2022-0513 is a critical-severity vulnerability; its CVE record was published on February 16, 2022. The WP Statistics WordPress plugin is vulnerable to SQL Injection due to insufficient escaping and parameterization of the exclusion_reason parameter found in the ~/includes/class-wp-statistics-exclusion.php file which allows attackers without authentication to inject arbitrary SQL queries to…
When was the CVE record for CVE-2022-0513 published?
The CVE record for CVE-2022-0513 was published on February 16, 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-0513 actively exploited?
CVE-2022-0513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 53% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-0513?
CVE-2022-0513 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-0513?
The CVE record's solution for CVE-2022-0513, written by its CNA Wordfence, names the fix: "Update to version 13.1.5 or newer."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-0513?

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