CVE-2024-58352

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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

Landray OA contains an unauthenticated HQL injection vulnerability that allows unauthenticated attackers to query arbitrary Hibernate entity classes by injecting malicious HQL syntax into the uid POST parameter of the wechatLoginHelper.do endpoint. Attackers can exploit the lack of input sanitization in the string-concatenated filter expression passed to the Hibernate findList() call to extract sensitive data such as administrator password hashes and, with sufficient database privileges, perform file-write operations enabling remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-03-11 (UTC).

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (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.

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

July 2, 2026

Last Modified

October 2, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
No fix on record yet.
Web page

Landray OA Unauthenticated HQL Injection via wechatLoginHelper.do | Advisories | VulnCheck

https://www.vulncheck.com/advisories/landray-oa-unauthenticated-hql-injection-via-wechatloginhelper-do

Vendor Advisories for CVE-2024-58352(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 9× in last 7d / 38× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 95 of 245 refreshes 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-58352?
CVE-2024-58352 is a high-severity vulnerability; its CVE record was published on July 2, 2026. Landray OA contains an unauthenticated HQL injection vulnerability that allows unauthenticated attackers to query arbitrary Hibernate entity classes by injecting malicious HQL syntax into the uid POST parameter of the wechatLoginHelper.do endpoint. Attackers can exploit the lack of input…
When was CVE-2024-58352 made public?
CVE-2024-58352 was made public on February 28, 2024: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 2, 2026. EchelonGraph's copy of the record carries a last-modified date of October 2, 2026; the record at its source may have been updated since.
Is CVE-2024-58352 actively exploited?
CVE-2024-58352 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-58352?
CVE-2024-58352 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2024-58352?
No fix for CVE-2024-58352 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2024-58352 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-58352

Explore →

Is Your Infrastructure Affected by CVE-2024-58352?

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

Book a Demo →Browse All CVEs