CVE-2018-16133 json
Cybrotech CyBroHttpServer 1.0.3 allows Directory Traversal via a ../ in the URI.
published 8y ago modified 4mo ago also EUVD-2018-7988
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 38.9%
- EPSS 38.9% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Cybrotech CyBroHttpServer 1.0.3 allows Directory Traversal via a ../ in the URI.
Is CVE-2018-16133 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-45303)
Exploit prediction
38.88% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45303 Cybrotech CyBroHttpServer 1.0.3 - Directory Traversal webapps, 2018-08-30
- Nuclei template Cybrotech CyBroHttpServer 1.0.3 - Local File Inclusion nuclei detection template
- emreovunc.com https://emreovunc.com/blog/en/CyBroHttpServer-v.1.0.3-Directory-Traversal-3.png referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/EmreOvunc/CyBroHttpServer-v1.0.3-Directory-Traversal referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/45303/
exploit, third-party-advisory, vdb-entry
-
emreovunc.com
/blog/en/CyBroHttpServer-v.1.0.3-Directory-Traversal-3.png
exploit, third-party-advisory
-
github.com
/EmreOvunc/CyBroHttpServer-v1.0.3-Directory-Traversal
exploit, third-party-advisory
Sources
- CVE List CVE-2018-16133
- NVD CVE-2018-16133
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.