Persistent cross-site scripting (XSS) issues in Jorani 0.6.5 allow remote attackers to inject arbitrary web script or HTML via the language parameter to session/language.
CVE-2018-15917
MEDIUMNVD 5.45.4—Elevated
EchelonGraph scoreMEDIUM confidence
Score 5.4 from GitHub Security Advisory published 2022-05-14. NVD baseline CVSS 5.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 5.9%CVSS: 5.4Exploit: Elevated riskExposed services: —
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
Internet exposure
The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.
- CVSS v3
- 5.4
- EG Score
- 5.4MEDIUMmedium confidence
- EG Risk
- 45EG Risk 45/100CISA SSVC
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 computedSeverity54% × 45%Exploitation40% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).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
- 5.9%
- EPSS %ILE
- 93rd
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* or 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 (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 5, 2018
Last Modified
November 21, 2024
References (6)
- cve@mitrehttps://github.com/bbalet/jorani/issues/254
- cve@mitrehttps://hackpuntes.com/cve-2018-15917-jorani-leave-management-system-0-6-5-cross-site-scripting-persistente/
- cve@mitrehttps://www.exploit-db.com/exploits/45338/
- af854a3a-2127-422b-91ae-364da2661108https://github.com/bbalet/jorani/issues/254
- af854a3a-2127-422b-91ae-364da2661108https://hackpuntes.com/cve-2018-15917-jorani-leave-management-system-0-6-5-cross-site-scripting-persistente/
- af854a3a-2127-422b-91ae-364da2661108https://www.exploit-db.com/exploits/45338/
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2018-15917?
CVE-2018-15917 is a medium vulnerability published on September 5, 2018. Persistent cross-site scripting (XSS) issues in Jorani 0.6.5 allow remote attackers to inject arbitrary web script or HTML via the language parameter to session/language.
When was CVE-2018-15917 disclosed?
CVE-2018-15917 was first published on September 5, 2018, 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-2018-15917 actively exploited?
CVE-2018-15917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.9% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-15917?
CVE-2018-15917 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2018-15917?
No fix for CVE-2018-15917 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.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2018-15917
Is Your Infrastructure Affected by CVE-2018-15917?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.