CVE-2019-7551 json
Cantemo Portal before 3.2.13, 3.3.x before 3.3.8, and 3.4.x before 3.4.9 has XSS.
published 7y ago modified 4mo ago also EUVD-2019-17090
- cvss
- 9.0
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Cantemo Portal before 3.2.13, 3.3.x before 3.3.8, and 3.4.x before 3.4.9 has XSS. Leveraging this vulnerability would enable performing actions as users, including administrative users. This could enable account creation and deletion as well as deletion of information contained within the app.
Patch / fix
- cantemo portal 3.2.13, 3.3.8, 3.4.9
Is CVE-2019-7551 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 FencerExploit prediction
1.73% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bishopfox.com https://www.bishopfox.com/news/2019/03/cantemo-portal-version-3-8-4-cross-site-scripting/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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-79 Improper Neutralization of Input During Web Page Generation
References
-
bishopfox.com
/news/2019/03/cantemo-portal-version-3-8-4-cross-site-scripting/
exploit, third-party-advisory
-
doc.cantemo.com
/latest/ReleaseNotes/intro.html#version-3-4-9
release-notes, vendor-advisory
-
blog-posts--cantemo.netlify.com
/news/2019/03/cantemo-portal-xss-vulnerabilities/
release-notes, vendor-advisory
-
bishopfox.com
/blog/news-category/advisories/
third-party-advisory
Sources
- CVE List CVE-2019-7551
- NVD CVE-2019-7551
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.