CVE-2017-15384: XSS
First published: Mon Oct 16 2017(Updated: )
rate-me.php in Rate Me 1.0 has XSS via the id field in a rate action.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PHPJabbers Rate Me | =1.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-15384?
CVE-2017-15384 has a high severity due to its potential for Cross-Site Scripting (XSS) attacks.
How do I fix CVE-2017-15384?
To fix CVE-2017-15384, sanitize and validate user inputs in the id field of the rate action in rate-me.php.
What systems are affected by CVE-2017-15384?
CVE-2017-15384 affects Rate Me version 1.0 from Phpjabbers.
What type of vulnerability is CVE-2017-15384?
CVE-2017-15384 is classified as a Cross-Site Scripting (XSS) vulnerability.
How can CVE-2017-15384 be exploited?
CVE-2017-15384 can be exploited by injecting malicious scripts through the id field in a rate action.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/weakness
- agent/last-modified-date
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/phpjabbers
- canonical/phpjabbers rate me
- version/phpjabbers rate me/1.0