CVE-2026-15510

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-07-13. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: Elevated riskExposed: 0

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

A vulnerability was found in Leantime up to 3.8.0. Affected is the function Setting::saveSetting of the component API. The manipulation results in improper authorization. The attack may be performed from remote. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
6.3
EG Score
6.3(high)
EG Risk
44(Track)
EG Risk 44/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
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

July 12, 2026

Last Modified

July 13, 2026

Advisory Details (1)

Auto-updated Jul 13, 2026
No patch confirmed yet.
generic

Leantime 3.8.0 Broken Access Control | Bytium

https://bytium.com/insights/leantime-3-8-0-broken-access-control

Vendor Advisories for CVE-2026-15510(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 31× 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-07-28 12:10 UTCEG score recompute
  2. 2026-07-28 12:10 UTCGHSA enrichment
  3. 2026-07-27 14:13 UTCEPSS rescore
  4. 2026-07-27 11:24 UTCEG score recompute
  5. 2026-07-27 11:24 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 12:00 UTCEG score recompute
  9. 2026-07-26 12:00 UTCGHSA enrichment
  10. 2026-07-25 14:17 UTCEPSS rescore
  11. 2026-07-24 14:17 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:05 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:30 UTCEPSS rescore
  17. 2026-07-19 02:28 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-16 20:22 UTCGHSA enrichment
  20. 2026-07-16 17:02 UTCEPSS rescore
  21. 2026-07-15 21:00 UTCGHSA enrichment
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-14 21:37 UTCGHSA enrichment
  25. 2026-07-13 22:30 UTCEPSS rescore
Show 6 more
  1. 2026-07-13 22:15 UTCGHSA enrichment
  2. 2026-07-13 18:08 UTCNVD updateCVSS v4 → 2.1
  3. 2026-07-13 16:22 UTCMITRE cvelistV5CVSS v4 → 5.3
  4. 2026-07-13 00:07 UTCNVD updateCVSS v4 → 2.1
  5. 2026-07-12 22:53 UTCEG score recompute
  6. 2026-07-12 22:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15510?
CVE-2026-15510 is a medium vulnerability published on July 12, 2026. A vulnerability was found in Leantime up to 3.8.0. Affected is the function Setting::saveSetting of the component API. The manipulation results in improper authorization. The attack may be performed from remote. The exploit has been made public and could be used. The vendor was contacted early…
When was CVE-2026-15510 disclosed?
CVE-2026-15510 was first published in the National Vulnerability Database on July 12, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15510 actively exploited?
CVE-2026-15510 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.2% of all scored CVEs.
What is the CVSS score of CVE-2026-15510?
CVE-2026-15510 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-15510?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15510, 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-2026-15510

Explore →

Is Your Infrastructure Affected by CVE-2026-15510?

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

Start Free Scan →Browse All CVEs