userSpice 4.3.24 POST Request existingUsernameCheck.php response discrepancy

Summaryinfo

A vulnerability labeled as problematic has been found in userSpice 4.3.24. Affected by this vulnerability is an unknown functionality of the file existingUsernameCheck.php of the component POST Request Handler. Such manipulation leads to response discrepancy. This vulnerability is traded as CVE-2018-25350. The attack may be launched remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in userSpice 4.3.24. It has been rated as problematic. Affected by this issue is an unknown part of the file existingUsernameCheck.php of the component POST Request Handler. The manipulation with an unknown input leads to a response discrepancy vulnerability. Using CWE to declare the problem leads to CWE-204. The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere. Impacted is confidentiality. CVE summarizes:

userSpice 4.3.24 contains a username enumeration vulnerability that allows unauthenticated attackers to discover valid usernames by sending POST requests to the existingUsernameCheck.php endpoint. Attackers can submit usernames and analyze response text for the 'taken' string to identify existing accounts in the system.

The weakness was shared by Dolev Farhi as 44872. The advisory is available at exploit-db.com. This vulnerability is handled as CVE-2018-25350 since 05/23/2026. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:existingUsernameCheck.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 databases at Exploit-DB (44872) and EUVD (EUVD-2018-21874). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• userSpice

Version

• 4.3.24

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion