VYPR
High severity8.2NVD Advisory· Published May 23, 2026· Updated May 26, 2026

CVE-2018-25348

CVE-2018-25348

Description

Unauthenticated SQL injection in Joomla! Component Ek Rishta 2.10 via cid parameter allows database extraction.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Unauthenticated SQL injection in Joomla! Component Ek Rishta 2.10 via cid parameter allows database extraction.

Vulnerability

The Joomla! Component Ek Rishta version 2.10 contains a SQL injection vulnerability in the user_detail view [1][2]. An unauthenticated attacker can inject arbitrary SQL commands through the cid parameter in a GET request. The component fails to properly sanitize user input before using it in a database query, leading to SQL injection. Affected versions are Ek Rishta <= 2.10 [1].

Exploitation

An attacker can exploit this vulnerability remotely without authentication. By sending a crafted GET request to the user_detail view with a malicious cid parameter containing SQL commands, the attacker can perform time-based blind SQL injection. For example, appending a payload like 1%' AND SLEEP(10)%23 causes a delay, confirming injection [2].

Impact

Successful exploitation allows an unauthenticated attacker to extract sensitive data from the database, including user credentials and other confidential information [1]. The impact is limited to information disclosure; no remote code execution or file modification is indicated.

Mitigation

As of the available references, no patched version has been released [1]. Users are advised to disable or remove the component if not essential, as there is no known vendor fix. The component may be discontinued or no longer supported [1].

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

4

News mentions

0

No linked articles in our index yet.