CVE-2018-25348: Joomla! Component Ek Rishta 2.10 SQL Injection via user_detail
Joomla! Component Ek Rishta 2.10 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the cid parameter. Attackers can send GET requests to the user_detail view with malicious cid values containing SQL commands to extract sensitive database information.
Security readout for executives and security teams
Plain-English summary
A Joomla add-on called Ek Rishta (version 2.10) has a flaw that lets anyone on the internet tamper with database queries by adjusting a value in the page URL. Without logging in, an attacker can pull sensitive data out of the site's database. Public exploit code has existed since 2018, making opportunistic scanning likely for exposed sites.
Executive priority
Treat as high priority only if a Joomla site running Ek Rishta 2.10 is in the environment; otherwise informational. Any exposed instance risks unauthenticated database disclosure, including personally identifiable data typical of matrimonial sites, warranting prompt containment.
Technical view
Ek Rishta 2.10 for Joomla contains an unauthenticated SQL injection (CWE-89) in the user_detail view via the cid GET parameter. Untrusted input is concatenated into a SQL query, allowing UNION-based or boolean extraction of database contents. CVSS v4.0 is scored 8.8 with network attack vector, no privileges, and no user interaction, per the source bundle.
Likely exposure
Exposure is limited to Joomla sites running Harmis Technology's Ek Rishta matrimonial component at version 2.10 that are internet-reachable. The component is a niche third-party extension, so the overall install base is likely small, but any exposed instance is directly reachable and unauthenticated.
Exploitation context
Public exploit code has been available on Exploit-DB (44869) since 2018, so proof-of-concept access is trivial for attackers. The CVE is not listed in CISA KEV and the sources do not confirm active in-the-wild exploitation, but the age and simplicity make opportunistic scanning realistic.
Researcher notes
Root cause is unsanitized use of the cid parameter in the user_detail SQL query. ExploitDB 44869 documents the injection point and payload shape. No vendor advisory or patched version is cited in the bundle; confirm status directly with Harmis Technology. Consider testing with sqlmap in an authorized lab against a mirrored install rather than production.
Mitigation direction
Inventory Joomla sites for the Ek Rishta component and identify any at version 2.10.
Consult the vendor (Harmis Technology / joomlaextensions.co.in) for a fixed release or guidance.
If no fix is available, disable or uninstall the Ek Rishta component until remediated.
Place a WAF rule in front of user_detail requests to block SQLi patterns on the cid parameter.
Restrict database account privileges used by Joomla to the minimum required.
Rotate database credentials if evidence of prior exploitation is found.
Validation and detection
Check Joomla Extension Manager for 'Ek Rishta' and record the installed version.
Review web server logs for GET requests to the user_detail view containing suspicious cid values or SQL syntax.
Inspect database audit or query logs for unexpected UNION, SLEEP, or information_schema activity.
Run an authenticated vulnerability scan against the site to confirm the SQLi finding and remediation.
Verify WAF or mitigation rules block known SQLi patterns without disrupting legitimate traffic.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.