Skip to content
Fencer Intel
medium 6.1

CVE-2017-15305 json

XSS exists in NexusPHP 1.5 via the keyword parameter to messages.php.

published 9y ago modified 4mo ago also EUVD-2017-6761

cvss
6.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

XSS exists in NexusPHP 1.5 via the keyword parameter to messages.php.

Is CVE-2017-15305 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

Exploit prediction

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

Exploits and checks

  • recorday.cn http://www.recorday.cn/about/xss2.txt referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/C0der1iu/Nexusphppoc/blob/master/xss2.txt 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.