CVE-2018-16836 in the critical feed json
Rubedo through 3.4.0 contains a Directory Traversal vulnerability in the theme component, allowing unauthenticated attackers to read and ex…
published 8y ago modified 4mo ago also EUVD-2018-8633
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 61.4%
- EPSS 61.4% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Rubedo through 3.4.0 contains a Directory Traversal vulnerability in the theme component, allowing unauthenticated attackers to read and execute arbitrary files outside of the service root path, as demonstrated by a /theme/default/img/%2e%2e/..//etc/passwd URI.
Is CVE-2018-16836 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-45385)
Exploit prediction
61.44% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45385 Rubedo CMS 3.4.0 - Directory Traversal webapps, 2018-09-12
- Nuclei template Rubedo CMS <=3.4.0 - Directory Traversal nuclei detection template
- github.com https://github.com/maroueneboubakri/CVE/tree/master/rubedo-cms referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/45385/
exploit, third-party-advisory, vdb-entry
-
github.com
/maroueneboubakri/CVE/tree/master/rubedo-cms
exploit, third-party-advisory
Sources
- CVE List CVE-2018-16836
- NVD CVE-2018-16836
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.