Serendipity 2.0.4 serendipity_admin.php serendipity[body] cross site scripting

Summaryinfo

A vulnerability classified as problematic has been found in Serendipity 2.0.4. This vulnerability affects unknown code of the file serendipity_admin.php. The manipulation of the argument serendipity[body] as part of Parameter leads to cross site scripting. This vulnerability is uniquely identified as CVE-2016-10737. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Serendipity 2.0.4 (Content Management System). This issue affects some unknown processing of the file serendipity_admin.php. The manipulation of the argument serendipity[body] as part of a Parameter leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

Serendipity 2.0.4 has XSS via the serendipity_admin.php serendipity[body] parameter.

The bug was discovered 10/29/2016. The weakness was disclosed 01/16/2019 as EDB-ID 40650 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2016-10737 since 01/15/2019. The attack may be initiated remotely. Required for exploitation is a simple authentication. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

After immediately, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 808 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:serendipity_admin.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (40650). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Name

• Serendipity

Version

• 2.0.4

License

• free

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion