CVE-2018-7315
Description
SQL Injection vulnerability in Ek Rishta 2.9 for Joomla! allows remote attackers to execute arbitrary SQL commands via multiple parameters.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
SQL Injection vulnerability in Ek Rishta 2.9 for Joomla! allows remote attackers to execute arbitrary SQL commands via multiple parameters.
Vulnerability
The Ek Rishta component version 2.9 for Joomla! is vulnerable to SQL Injection in the /index.php/component/ekrishta/alluser view. The gender, age1, age2, religion, mothertounge, caste, and country parameters are not properly sanitized before being used in SQL queries, allowing an attacker to inject malicious SQL code. [1]
Exploitation
An attacker can send HTTP GET requests to the vulnerable URL with specially crafted parameter values containing SQL injection payloads. The exploit-db entry provides a proof-of-concept URL demonstrating the injection. No authentication is required as the component is accessible. The attacker can use typical SQL injection techniques such as UNION or boolean-based blind injection. [1]
Impact
Successful exploitation allows an attacker to retrieve sensitive information from the database, such as user credentials or other data, potentially leading to full compromise of the Joomla! installation. The injection can also be used to modify or delete data, depending on database permissions. [1]
Mitigation
No official patch or update has been released for Ek Rishta 2.9 as per the available references. Users are advised to disable or remove the component until a fix is available, or implement input validation and parameterized queries manually. [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
2= 2.9+ 1 more
- (no CPE)range: = 2.9
- (no CPE)range: =2.9
Patches
0No 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
1- exploit-db.com/exploits/44161mitreexploitx_refsource_EXPLOIT-DB
News mentions
0No linked articles in our index yet.