An issue was discovered in GitStack through 2.3.10. User controlled input is not sufficiently filtered, allowing an unauthenticated attacker to add a user to the server via the username and password fields to the rest/user/ URI.
CVE-2018-5955
“—” beside the score: it is equal to NVD's CVSS score.
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.
Also known asEUVD-2018-17722 (ENISA EUVD) · GHSA-fxv2-2mqx-vqg2 (GitHub Security Advisories)Source: ENISA EUVD
- High exploitation likelihood — EPSS 82%
- Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB, other public proof-of-concept code)
No fix has been recorded since the CVE record was published in 2018 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
The CVE record's description, written by its CNA (MITRE Corporation), states the affected versions: "An issue was discovered in GitStack through 2.3.10." No release containing a fix is confirmed on record.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALmedium confidence
- EG Risk
- 77EG Risk 77/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)Severity98% × 45%Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation82% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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 has been recorded since the CVE record was published in 2018. If the vendor still supports the product, apply the fixed version it names within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) on your normal schedule at low or medium mission impact and sooner than that at high, or retire the product. - EPSS PROB
- 82%
- EPSS %ILE
- 99th
- 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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 82% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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, Track* at medium and Attend at high mission impact.
No fix has been recorded since the CVE record was published in 2018. If the vendor still supports the product, apply the fixed version it names within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) on your normal schedule at low or medium mission impact and sooner than that at high, or retire the product.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.
No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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
January 21, 2018
Last Modified
November 21, 2024
Advisory Details (1)
Auto-updated Oct 6, 2026GitStack - Unsanitized Argument Remote Code Execution (Metasploit) - Windows remote Exploit
https://www.exploit-db.com/exploits/44356/Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 47× 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 189 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 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-22 13:15 UTCEchelonGraph re-scored
- 2026-11-22 13:15 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-21 15:34 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-20 17:56 UTCEchelonGraph re-scored
- 2026-11-20 17:56 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-19 20:18 UTCEchelonGraph re-scored
- 2026-11-19 20:17 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-19 16:27 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-11-18 22:38 UTCEchelonGraph re-scored
- 2026-11-18 22:38 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-18 01:00 UTCEchelonGraph re-scored
- 2026-11-18 01:00 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-17 03:22 UTCEchelonGraph re-scored
- 2026-11-17 03:22 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-16 05:41 UTCEchelonGraph re-scored
- 2026-11-16 05:41 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-15 16:38 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-11-15 06:56 UTCEchelonGraph re-scored
- 2026-11-15 06:56 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-14 09:18 UTCEchelonGraph re-scored
- 2026-11-14 09:18 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-13 16:37 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-11-13 11:40 UTCEchelonGraph re-scored
- 2026-11-13 11:40 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-12 14:01 UTCEchelonGraph re-scored
Show 75 moreShow fewer
- 2026-11-12 14:01 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-11 16:30 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-11-11 16:24 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-10 18:43 UTCEchelonGraph re-scored
- 2026-11-10 18:43 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-10 16:32 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-11-09 21:00 UTCEchelonGraph re-scored
- 2026-11-09 21:00 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-08 23:23 UTCEchelonGraph re-scored
- 2026-11-08 23:23 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-08 01:45 UTCEchelonGraph re-scored
- 2026-11-08 01:45 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-07 04:08 UTCEchelonGraph re-scored
- 2026-11-07 04:08 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-06 06:26 UTCEchelonGraph re-scored
- 2026-11-06 06:26 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-05 16:28 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-11-05 08:49 UTCEchelonGraph re-scored
- 2026-11-05 08:49 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-04 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-11-04 11:11 UTCEchelonGraph re-scored
- 2026-11-04 11:11 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-03 16:35 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-11-03 13:33 UTCEchelonGraph re-scored
- 2026-11-03 13:33 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-02 16:35 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-11-02 15:36 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-01 17:58 UTCEchelonGraph re-scored
- 2026-11-01 17:58 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-31 20:18 UTCEchelonGraph re-scored
- 2026-10-31 20:18 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-31 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-30 22:41 UTCEchelonGraph re-scored
- 2026-10-30 22:41 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-30 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-30 01:04 UTCEchelonGraph re-scored
- 2026-10-30 01:04 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-29 03:26 UTCEchelonGraph re-scored
- 2026-10-29 03:25 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-28 05:48 UTCEchelonGraph re-scored
- 2026-10-28 05:48 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-27 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-27 08:11 UTCEchelonGraph re-scored
- 2026-10-27 08:11 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-26 08:17 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-25 19:16 UTCEchelonGraph re-scored
- 2026-10-25 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-25 10:39 UTCEchelonGraph re-scored
- 2026-10-25 10:39 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-24 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-24 13:01 UTCEchelonGraph re-scored
- 2026-10-24 13:01 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-23 15:13 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-22 17:25 UTCEchelonGraph re-scored
- 2026-10-22 17:25 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-21 19:43 UTCEchelonGraph re-scored
- 2026-10-21 19:43 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-21 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-20 22:04 UTCEchelonGraph re-scored
- 2026-10-20 22:04 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-20 00:24 UTCEchelonGraph re-scored
- 2026-10-20 00:24 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-19 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-18 23:14 UTCEchelonGraph re-scored
- 2026-10-18 23:14 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-18 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-18 10:05 UTCEchelonGraph re-scored
- 2026-10-18 01:35 UTCEchelonGraph re-scored
- 2026-10-18 01:35 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-17 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-17 03:14 UTCEchelonGraph re-scored
- 2026-10-17 03:14 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-16 05:35 UTCEchelonGraph re-scored
- 2026-10-16 05:35 UTCGHSA enrichmentGHSA-fxv2-2mqx-vqg2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-15 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
Publicly available exploits
(6 references)Public exploit code is referenced for this CVE (2 Metasploit modules, 2 Exploit-DB entries, 2 GitHub PoCs). No fix has been recorded since the CVE record was published in 2018. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system or retire the product.
- Metasploitauxiliary/admin/http/gitstack_rest✓ verifiedPublished Apr 23, 2018
GitStack Unauthenticated REST API Requests
Open source ↗ - Exploit-DBEDB-44356✓ verifiedPublished Mar 29, 2018
GitStack - Unsanitized Argument Remote Code Execution (Metasploit)
Open source ↗ - Metasploitexploit/windows/http/gitstack_rce✓ verifiedPublished Mar 27, 2018
GitStack Unsanitized Argument RCE
Open source ↗ - GitHub PoCMikeTheHash/CVE-2018-5955Published Jun 23, 2023
An exploit for CVE-2018-5955 GitStack 2.3.10 Unauthenticated RCE
Open source ↗ - GitHub PoCYagamiiLight/CerberusPublished Dec 21, 2019
一款功能强大的漏洞扫描器,子域名爆破使用aioDNS,asyncio异步快速扫描,覆盖目标全方位资产进行批量漏洞扫描,中间件信息收集,自动收集ip代理,探测Waf信息时自动使用来保护本机真实Ip,在本机Ip被Waf杀死后,自动切换代理Ip进行扫描,Waf信息收集(国内外100+款waf信息)包括安全狗,云锁,阿里云,云盾,腾讯云等,提供部分已知waf bypass 方案,中间件漏洞检测(Thinkphp,weblogic等 CVE-2018-5955,CVE-2018-12613,CVE-2018-11759等),支持SQL注入, XSS, 命令执行,文件包含, ssrf 漏洞扫描, 支持自定义漏洞邮箱推送功能
Open source ↗ - Exploit-DBEDB-44044Published Jan 15, 2018
GitStack - Remote Code Execution
Open source ↗
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2018-5955?
When was CVE-2018-5955 made public?
Is CVE-2018-5955 actively exploited?
What is the CVSS score of CVE-2018-5955?
How do I remediate CVE-2018-5955?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2018-5955
Is Your Infrastructure Affected by CVE-2018-5955?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.