CVE-2017-18195 json
An issue was discovered in tools/conversations/view_ajax.php in Concrete5 before 8.3.0.
published 8y ago modified 4mo ago also EUVD-2017-9329
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.1%
- EPSS 11.1% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered in tools/conversations/view_ajax.php in Concrete5 before 8.3.0. An unauthenticated user can enumerate comments from all blog posts by POSTing requests to /index.php/tools/required/conversations/view_ajax with incremental 'cnvID' integers.
Patch / fix
- concretecms concrete_cms 8.3.0
- github.com/concrete5/concrete5#6008 pull request
- github.com/concrete5/concrete5/releases/tag/8.3.0 release
Is CVE-2017-18195 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-44194)
Exploit prediction
11.05% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44194 Concrete5 CMS < 8.3.0 - Username / Comments Enumeration webapps, 2018-02-27
- github.com https://github.com/r3naissance/NSE/blob/master/http-vuln-cve2017-18195.nse referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/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 |
References
-
github.com
/concrete5/concrete5/pull/6008/files
patch, third-party-advisory
-
exploit-db.com
/exploits/44194/
exploit, third-party-advisory, vdb-entry
-
github.com
/r3naissance/NSE/blob/master/http-vuln-cve2017-18195.nse
exploit, third-party-advisory
-
github.com
/concrete5/concrete5/releases/tag/8.3.0
release-notes, third-party-advisory
Sources
- CVE List CVE-2017-18195
- NVD CVE-2017-18195
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.