Skip to content
Fencer Intel
medium 6.1

CVE-2018-5715 json

phprint.php in SugarCRM 3.5.1 has XSS via a parameter name in the query string (aka a $key variable).

published 8y ago modified 4mo ago also EUVD-2018-17484

cvss
6.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.9%
EPSS 6.9% chance of exploitation in 30 days, percentile 94%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

phprint.php in SugarCRM 3.5.1 has XSS via a parameter name in the query string (aka a $key variable).

Is CVE-2018-5715 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 Fencer

Timeline

  1. Published
  2. First public exploit (EDB-43683)

Exploit prediction

6.91% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-43683 SugarCRM 3.5.1 - Cross-Site Scripting webapps, 2018-01-17
  • Nuclei template SugarCRM 3.5.1 - Cross-Site Scripting nuclei detection template
  • m4k4br0.github.io https://m4k4br0.github.io/sugarcrm-xss/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 6.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

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.