CVE-2020-27615

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 53.6%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 52%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 52%CVSS: 9.8Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Loginizer plugin before 1.6.4 for WordPress allows SQL injection (with resultant XSS), related to loginizer_login_failed and lz_valid_ip.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track*)
EG Risk 75/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
52%
EPSS %ILE
99%
KEV
Not listed

Published

October 21, 2020

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Aug 15, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

WordPress deploys forced security update for dangerous bug in popular plugin | ZDNET

https://www.zdnet.com/article/wordpress-deploys-forced-security-update-for-dangerous-bug-in-popular-plugin/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:52 UTCEPSS rescore
  2. 2026-08-19 17:00 UTCEPSS rescore
  3. 2026-08-18 13:44 UTCEPSS rescore
  4. 2026-08-17 13:43 UTCEPSS rescore
  5. 2026-08-16 14:52 UTCEPSS rescore
  6. 2026-08-16 02:11 UTCEPSS rescore
  7. 2026-08-15 01:26 UTCEPSS rescore
  8. 2026-08-12 13:47 UTCEPSS rescore
  9. 2026-08-07 16:23 UTCEPSS rescore
  10. 2026-08-06 13:43 UTCEPSS rescore
  11. 2026-08-04 15:06 UTCEPSS rescore
  12. 2026-08-04 10:34 UTCEPSS rescore
  13. 2026-07-30 16:25 UTCEPSS rescore
  14. 2026-07-30 01:27 UTCEPSS rescore
  15. 2026-07-28 15:33 UTCEPSS rescore
  16. 2026-07-26 14:51 UTCEPSS rescore
  17. 2026-07-25 14:15 UTCEPSS rescore
  18. 2026-07-24 14:14 UTCEPSS rescore
  19. 2026-07-23 14:15 UTCEPSS rescore
  20. 2026-07-23 14:15 UTCEPSS rescore
  21. 2026-07-23 01:52 UTCEG score recompute
  22. 2026-07-22 22:38 UTCEG score recompute
  23. 2026-07-22 14:05 UTCEPSS rescore
  24. 2026-07-21 15:22 UTCEPSS rescore
  25. 2026-07-21 15:22 UTCEPSS rescore
Show 53 more
  1. 2026-07-20 17:04 UTCEPSS rescore
  2. 2026-07-20 17:04 UTCEPSS rescore
  3. 2026-07-19 02:26 UTCEPSS rescore
  4. 2026-07-19 02:26 UTCEPSS rescore
  5. 2026-07-16 16:59 UTCEPSS rescore
  6. 2026-07-15 16:55 UTCEPSS rescore
  7. 2026-07-15 16:55 UTCEPSS rescore
  8. 2026-07-13 06:10 UTCEPSS rescore
  9. 2026-07-13 06:10 UTCEPSS rescore
  10. 2026-07-12 05:44 UTCEPSS rescore
  11. 2026-07-11 08:25 UTCEPSS rescore
  12. 2026-07-11 08:25 UTCEPSS rescore
  13. 2026-07-09 19:07 UTCEPSS rescore
  14. 2026-07-06 02:21 UTCEPSS rescore
  15. 2026-07-06 02:21 UTCEPSS rescore
  16. 2026-06-30 23:20 UTCEPSS rescore
  17. 2026-06-30 23:20 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-28 04:54 UTCEPSS rescore
  20. 2026-06-27 03:06 UTCEPSS rescore
  21. 2026-06-27 03:06 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
  26. 2026-06-18 17:50 UTCEPSS rescore
  27. 2026-06-18 17:50 UTCEPSS rescore
  28. 2026-06-17 17:50 UTCEPSS rescore
  29. 2026-06-16 17:50 UTCEPSS rescore
  30. 2026-06-15 17:46 UTCEPSS rescore
  31. 2026-06-13 22:58 UTCEPSS rescore
  32. 2026-06-12 23:10 UTCEPSS rescore
  33. 2026-06-10 22:16 UTCEPSS rescore
  34. 2026-06-10 13:20 UTCEPSS rescore
  35. 2026-06-08 14:15 UTCEPSS rescore
  36. 2026-06-06 13:46 UTCEPSS rescore
  37. 2026-06-06 13:45 UTCEPSS rescore
  38. 2026-06-05 22:45 UTCEPSS rescore
  39. 2026-06-05 22:45 UTCEPSS rescore
  40. 2026-06-04 13:10 UTCEPSS rescore
  41. 2026-06-04 13:10 UTCEPSS rescore
  42. 2026-06-01 13:50 UTCEPSS rescore
  43. 2026-05-31 22:29 UTCEPSS rescore
  44. 2026-05-31 22:29 UTCEPSS rescore
  45. 2026-05-29 13:42 UTCEPSS rescore
  46. 2026-05-28 13:43 UTCEPSS rescore
  47. 2026-05-28 13:43 UTCEPSS rescore
  48. 2026-05-27 13:39 UTCEPSS rescore
  49. 2026-05-27 13:39 UTCEPSS rescore
  50. 2026-05-26 07:17 UTCEPSS rescore
  51. 2026-05-26 07:17 UTCEPSS rescore
  52. 2026-05-23 06:13 UTCEG score recompute
  53. 2026-05-23 06:13 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitauxiliary/scanner/http/wp_loginizer_log_sqli✓ verified
    First seen Oct 21, 2020

    WordPress Loginizer log SQLi Scanner

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-27615.yaml
    First seen Jan 1, 2020

    WordPress Loginizer < 1.6.4 – Unauthenticated SQL Injection via `log` Parameter

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-27615?
CVE-2020-27615 is a critical vulnerability published on October 21, 2020. The Loginizer plugin before 1.6.4 for WordPress allows SQL injection (with resultant XSS), related to loginizerloginfailed and lzvalidip.
When was CVE-2020-27615 disclosed?
CVE-2020-27615 was first published in the National Vulnerability Database on October 21, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-27615 actively exploited?
CVE-2020-27615 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52% probability of exploitation in the next 30 days, which ranks it in the top 1.1% of all scored CVEs.
What is the CVSS score of CVE-2020-27615?
CVE-2020-27615 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-27615?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-27615, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-27615

Explore →

Is Your Infrastructure Affected by CVE-2020-27615?

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

Start Free Scan →Browse All CVEs