Is CVE-2017-5476 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2017-5476 being exploited in the wild.

How severe is CVE-2017-5476?

High severity, with a CVSS score of 8.8, published 14 January 2017.

Which products and versions are affected?

Serendipity up to and including 2.0.5.

Is there a fix for CVE-2017-5476?

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-5476 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2017-5476?

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.

CVE-2017-5476: Serendipity CSRF in plugin installation

CVE-2017-5476 · Severity: high · CVSS 8.8 · Published 2017-01-14

Serendipity, a popular weblog engine, contains a security flaw that could allow an attacker to trick an administrator into performing unintended actions. Specifically, an attacker can force the installation of unauthorized event or sidebar plugins if a logged-in administrator visits a malicious website. This could lead to unauthorized changes to the website's functionality or the introduction of malicious code through rogue plugins.

Technologies: Serendipity. Vendors: Serendipity.

Quick answers

Is CVE-2017-5476 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-5476 being exploited in the wild.
How severe is CVE-2017-5476?: High severity, with a CVSS score of 8.8, published 14 January 2017.
Which products and versions are affected?: Serendipity up to and including 2.0.5.
Is there a fix for CVE-2017-5476?: 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-5476 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-5476?: 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 insufficient validation of request tokens when installing plugins. An attacker can craft a malicious web page that, when visited by an authenticated administrator, triggers a background request to the Serendipity administrative interface to install a specific event or sidebar plugin. This occurs because the application does not properly verify that the request was intentionally initiated by the user. Successful exploitation allows an attacker to modify the blog's behavior or potentially achieve further compromise by installing plugins with malicious capabilities. The issue was addressed in subsequent updates by implementing CSRF token checks.

Affected products

s9y Serendipity up to and including 2.0.5

Timeline

2017-01-12: disclosed: Issue reported on GitHub repository
2017-01-14: advisory: NVD published CVE-2017-5476

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.