Springsignage Xibo 1.4.2 index.php cross-site request forgery

Summaryinfo

A vulnerability marked as problematic has been reported in Springsignage Xibo 1.4.2. This vulnerability affects unknown code of the file index.php. The manipulation leads to cross-site request forgery. This vulnerability is referenced as CVE-2013-4889. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability was found in Springsignage Xibo 1.4.2 and classified as critical. This issue affects an unknown code of the file index.php. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Multiple cross-site request forgery (CSRF) vulnerabilities in index.php in Digital Signage Xibo 1.4.2 allow remote attackers to hijack the authentication of administrators for requests that (1) add a new administrator via the AddUser action or (2) conduct cross-site scripting (XSS) attacks, as demonstrated by CVE-2013-4888.

The weakness was published 01/29/2014 (Website). The advisory is shared at infosec42.blogspot.com. The identification of this vulnerability is CVE-2013-4889 since 07/22/2013. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:index.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 (38746). Similar entry is available at VDB-66244. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Springsignage

Name

• Xibo

Version

• 1.4.2

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion