harmistechnology Ek Rishta 2.10 Login Endpoint Username sql injection

Summaryinfo

A vulnerability was found in harmistechnology Ek Rishta 2.10. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component Login Endpoint. This manipulation of the argument Username causes sql injection. This vulnerability is registered as CVE-2018-25351. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability classified as critical was found in harmistechnology Ek Rishta 2.10. Affected by this vulnerability is an unknown function of the component Login Endpoint. The manipulation of the argument username with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Joomla! Component EkRishta 2.10 contains an error-based SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code into the username parameter. Attackers can submit POST requests to the login endpoint with SQL injection payloads in the username field to extract database information including user credentials and system details.

The weakness was published by L0RD as 44877. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2018-25351 since 05/23/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.

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 (44877) and EUVD (EUVD-2018-21873). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• harmistechnology

Name

• Ek Rishta

Version

• 2.10

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