CVE-2026-42647

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-12. A secondary CVSS source baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-36359 (ENISA EUVD) · GHSA-2369-78ph-422f (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
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 severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 9.3Exploit: None knownExposed services: Not assessed

Update the WordPress JoomSport Plugin to the latest available version (at least 5.7.8) (from the CVE record's solution, Patchstack) — apply it.

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Beardev JoomSport allows Blind SQL Injection.

This issue affects JoomSport: from n/a through 5.7.7.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.3% × 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 partial (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 the WordPress JoomSport Plugin to the latest available version (at least 5.7.8) (from the CVE record's solution, Patchstack). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.3%
EPSS %ILE
71st
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.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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: 14 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 the WordPress JoomSport Plugin to the latest available version (at least 5.7.8) (from the CVE record's solution, Patchstack). 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 partial (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)14 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 partial (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

June 11, 2026

Last Modified

October 26, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
Fix named in the CVE record's solution (Patchstack).

Vendor Advisories for CVE-2026-42647(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× 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 522 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 422 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  2. 2026-11-12 15:59 UTCEchelonGraph re-scored
  3. 2026-11-12 15:59 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  4. 2026-11-11 16:39 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  5. 2026-11-11 14:11 UTCEchelonGraph re-scored
  6. 2026-11-11 14:11 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  7. 2026-11-10 16:44 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  8. 2026-11-10 12:25 UTCEchelonGraph re-scored
  9. 2026-11-10 12:25 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  10. 2026-11-09 16:35 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  11. 2026-11-09 10:41 UTCEchelonGraph re-scored
  12. 2026-11-09 10:41 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  13. 2026-11-08 16:39 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  14. 2026-11-08 08:57 UTCEchelonGraph re-scored
  15. 2026-11-08 08:57 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  16. 2026-11-07 16:39 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  17. 2026-11-07 07:12 UTCEchelonGraph re-scored
  18. 2026-11-07 07:12 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  19. 2026-11-06 16:37 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  20. 2026-11-06 05:25 UTCEchelonGraph re-scored
  21. 2026-11-06 05:25 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  22. 2026-11-05 16:37 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  23. 2026-11-05 03:41 UTCEchelonGraph re-scored
  24. 2026-11-05 03:41 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  25. 2026-11-04 16:35 UTCEPSS rescoreEPSS 1.3% · 70th percentile
Show 75 more
  1. 2026-11-04 01:56 UTCEchelonGraph re-scored
  2. 2026-11-04 01:56 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  3. 2026-11-03 16:48 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  4. 2026-11-03 00:12 UTCEchelonGraph re-scored
  5. 2026-11-03 00:12 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  6. 2026-11-02 16:44 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  7. 2026-11-01 22:25 UTCEchelonGraph re-scored
  8. 2026-11-01 22:25 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  9. 2026-11-01 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  10. 2026-10-31 20:41 UTCEchelonGraph re-scored
  11. 2026-10-31 20:41 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  12. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  13. 2026-10-30 18:57 UTCEchelonGraph re-scored
  14. 2026-10-30 18:57 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  15. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  16. 2026-10-29 17:12 UTCEchelonGraph re-scored
  17. 2026-10-29 17:12 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  18. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  19. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  20. 2026-10-28 15:28 UTCEchelonGraph re-scored
  21. 2026-10-28 15:28 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  22. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  23. 2026-10-27 13:43 UTCEchelonGraph re-scored
  24. 2026-10-27 13:43 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  25. 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  26. 2026-10-26 11:26 UTCEchelonGraph re-scored
  27. 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  28. 2026-10-25 14:29 UTCEchelonGraph re-scored
  29. 2026-10-25 10:07 UTCEchelonGraph re-scored
  30. 2026-10-25 10:07 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  31. 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  32. 2026-10-24 08:21 UTCEchelonGraph re-scored
  33. 2026-10-24 08:21 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  34. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  35. 2026-10-23 06:36 UTCEchelonGraph re-scored
  36. 2026-10-23 06:36 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  37. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  38. 2026-10-22 04:52 UTCEchelonGraph re-scored
  39. 2026-10-22 04:51 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  40. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  41. 2026-10-21 03:07 UTCEchelonGraph re-scored
  42. 2026-10-21 03:06 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  43. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  44. 2026-10-20 01:19 UTCEchelonGraph re-scored
  45. 2026-10-20 01:19 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  46. 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  47. 2026-10-18 23:35 UTCEchelonGraph re-scored
  48. 2026-10-18 23:35 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  49. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  50. 2026-10-18 03:40 UTCEchelonGraph re-scored
  51. 2026-10-17 21:51 UTCEchelonGraph re-scored
  52. 2026-10-17 21:50 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  53. 2026-10-17 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  54. 2026-10-16 20:05 UTCEchelonGraph re-scored
  55. 2026-10-16 20:04 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  56. 2026-10-16 16:42 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  57. 2026-10-15 17:39 UTCEchelonGraph re-scored
  58. 2026-10-15 17:39 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  59. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  60. 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  61. 2026-10-14 11:31 UTCEchelonGraph re-scored
  62. 2026-10-14 11:31 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  63. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  64. 2026-10-13 09:42 UTCEchelonGraph re-scored
  65. 2026-10-13 09:42 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  66. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  67. 2026-10-12 16:07 UTCEchelonGraph re-scored
  68. 2026-10-12 07:56 UTCGHSA enrichmentGHSA-2369-78ph-422f · GitHub severity CRITICAL · GitHub CVSS 9.3
  69. 2026-10-11 19:49 UTCEchelonGraph re-scored
  70. 2026-10-11 17:03 UTCEchelonGraph re-scored
  71. 2026-10-11 14:29 UTCEchelonGraph re-scored
  72. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  73. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  74. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  75. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.3% · 70th 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/2026/CVE-2026-42647.yaml
    Published Jun 1, 2026

    JoomSport <= 5.7.7 - SQL Injection

    Open source ↗

Frequently asked(5)

What is CVE-2026-42647?
CVE-2026-42647 is a critical-severity vulnerability; its CVE record was published on June 11, 2026. Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Beardev JoomSport allows Blind SQL Injection. This issue affects JoomSport: from n/a through 5.7.7.
When was the CVE record for CVE-2026-42647 published?
The CVE record for CVE-2026-42647 was published on June 11, 2026. 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 October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-42647 actively exploited?
CVE-2026-42647 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (71st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42647?
CVE-2026-42647 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42647?
The CVE record's solution for CVE-2026-42647, written by its CNA Patchstack, names the fix: "Update the WordPress JoomSport Plugin to the latest available version (at least 5.7.8)." The vendor advisories EchelonGraph has for CVE-2026-42647 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42647

Explore →

Is Your Infrastructure Affected by CVE-2026-42647?

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