CVE-2018-7216 json
Cross-site request forgery (CSRF) vulnerability in esop/toolkit/profile/regData.do in Bravo Tejari Procurement Portal allows remote authent…
published 2018-02-18 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-18955
- cvss
- 8.0
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 86%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site request forgery (CSRF) vulnerability in esop/toolkit/profile/regData.do in Bravo Tejari Procurement Portal allows remote authenticated users to hijack the authentication of application users for requests that modify their personal data by leveraging lack of anti-CSRF tokens.
Timeline
- Published
- First public exploit (EDB-44256)
Exploit prediction
2.86% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44256 Bravo Tejari Web Portal - Cross-Site Request Forgery webapps, 2018-03-06
- seclists.org http://seclists.org/fulldisclosure/2018/Feb/44 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com https://packetstormsecurity.com/files/146409/Tejari-Cross-Site-Request-Forgery.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.0 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
exploit-db.com
/exploits/44256/
exploit, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2018/Feb/44
exploit, mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/146409/Tejari-Cross-Site-Request-Forgery.html
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/archive/1/541782/30/0/threaded
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2018-7216
- NVD CVE-2018-7216
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.