Quick answers
- Is CVE-2017-5475 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-5475 being exploited in the wild.
- How severe is CVE-2017-5475?
- High severity, with a CVSS score of 8.8, published 14 January 2017.
- Which products and versions are affected?
- Serendipity through 2.0.5.
- Is there a fix for CVE-2017-5475?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2017-5475 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2017-5475?
- Check whether you run Serendipity at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Cross-Site Request Forgery (CSRF) vulnerability exists in Serendipity through version 2.0.5 due to a failure to validate CSRF tokens in the comment.php script. Specifically, the serendipity_deleteComment function can be invoked via a crafted HTTP request without verifying the authenticity of the request origin. An attacker can exploit this by inducing an authenticated administrator to visit a malicious webpage, resulting in the deletion of arbitrary comments. The issue was addressed by implementing token verification for comment deletion actions.
Affected products
- s9y Serendipity through 2.0.5
Timeline
- 2017-01-12: disclosed: Issue reported on GitHub by Lee Sheldon Victor
- 2017-01-14: advisory: NVD publication date