CVE-2018-16606 json
In ProConf before 6.1, an Insecure Direct Object Reference (IDOR) allows any author to view and grab all submitted papers (Title and Abstra…
published 2018-09-06 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-8413
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.9%
- EPSS 5.9% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
In ProConf before 6.1, an Insecure Direct Object Reference (IDOR) allows any author to view and grab all submitted papers (Title and Abstract) and their authors' personal information (Name, Email, Organization, and Position) by changing the value of Paper ID (the pid parameter).
Patch / fix
- proconf proconf 6.1
Timeline
- Published
- First public exploit (EDB-52236)
Exploit prediction
5.95% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-52236 ProConf 6.0 - Insecure Direct Object Reference (IDOR) webapps, 2025-04-16
- blog.ziaurrashid.com https://blog.ziaurrashid.com/idor-on-proconf-peer-reviewand-conference-management-system/ referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com https://packetstormsecurity.com/files/149259/IDOR-On-ProConf-Peer-Review-And-Conference-Management-6.0-File-Disclosure.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
blog.ziaurrashid.com
/idor-on-proconf-peer-reviewand-conference-management-system/
exploit, third-party-advisory
-
packetstormsecurity.com
/files/149259/IDOR-On-ProConf-Peer-Review-And-Conference-Management-6.0-File-Disclosure.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2018-16606
- NVD CVE-2018-16606
Fencer Vulns 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.