CVE-2018-25330: Joomla! EkRishta 2.10 Persistent XSS and SQL Injection
Joomla! extension EkRishta 2.10 contains persistent cross-site scripting and SQL injection vulnerabilities that allow attackers to inject malicious code through profile fields and POST parameters. Attackers can inject script payloads in profile information fields like Address that execute when users visit the profile, or submit SQL injection payloads via the phone_no parameter to the user_setting endpoint to manipulate database queries.
Security readout for executives and security teams
Plain-English summary
CVE-2018-25330 affects the Joomla! EkRishta 2.10 extension. The reported issues could let unauthenticated attackers store script content in profile fields or influence database queries through a POST parameter. For exposed Joomla sites using this extension, the business risk is account, data, and trust impact.
Executive priority
High priority for any organization running EkRishta 2.10 on a public Joomla site. The combination of stored XSS, SQL injection, unauthenticated reachability, and public exploit reference warrants prompt inventory, containment, and vendor-guidance review.
Technical view
The source bundle reports persistent XSS in profile information fields such as Address and SQL injection through the phone_no parameter on the user_setting endpoint. The CVSS 4.0 score is 8.8. Sources identify EkRishta 2.10 only; no broader version range or CPE is provided.
Likely exposure
Exposure is likely limited to Joomla websites running the EkRishta dating and relationships extension version 2.10, especially public community or dating sites with user profiles enabled. Evidence does not identify affected Joomla core versions or other EkRishta releases.
Exploitation context
A public ExploitDB reference exists, so technical details are publicly known. The bundle marks KEV as false and provides no cited evidence of active exploitation. Treat as exposed-risk, not confirmed in-the-wild exploitation.
Researcher notes
The source bundle is specific but incomplete on remediation. It identifies EkRishta 2.10, persistent XSS, SQL injection, affected parameters, and public exploit reference. It does not provide a vendor patch version, CPE, active exploitation evidence, or affected-version range beyond 2.10.
Mitigation direction
Inventory Joomla sites for EkRishta 2.10 installations.
Check Joomlaextensions or official vendor guidance for a fixed release.
If no supported fix exists, disable or remove EkRishta.
Prioritize internet-facing sites with public profile functionality.
Inspect stored profile content and database records for tampering.
Validation and detection
Confirm extension name and version in Joomla extension inventory.
Identify routes exposing EkRishta profiles and user settings.
Review profile fields, especially Address, for unauthorized script content.
Review logs for unusual POST activity involving user_setting and phone_no.
Validate remediation in a test environment before production rollout.
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.