CVE-2018-25351: Joomla! Component EkRishta 2.10 SQL Injection via username
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.
Security readout for executives and security teams
Plain-English summary
A third-party Joomla add-on called EkRishta (version 2.10) has a flaw in its login page that lets an unauthenticated attacker trick the database into running attacker-supplied queries. In practical terms, someone on the internet could pull user records, credentials, or other stored data from any site that uses this component, without needing an account.
Executive priority
Prioritize this above routine patching if any customer-facing Joomla site uses the EkRishta component. Exploitation is unauthenticated, public exploit code exists, and a successful attack can leak customer credentials — a likely reportable data event. If the extension is not deployed, priority drops to informational tracking.
Technical view
CVE-2018-25351 is an error-based SQL injection (CWE-89) in the Joomla! EkRishta 2.10 component. The username POST parameter on the login endpoint is passed unsanitized into a SQL statement, allowing an unauthenticated remote attacker to alter query logic and enumerate database contents. A public proof-of-concept exists in ExploitDB (44877). CVSS v4.0 is scored 8.8 (high) with network attack vector and no privileges required.
Likely exposure
Any internet-facing Joomla site running the EkRishta 2.10 component (a matrimonial/dating extension) is exposed. Exposure is limited to organizations that installed this specific third-party extension; core Joomla installations without it are unaffected. Public exploit availability raises the probability of opportunistic scanning against Joomla sites.
Exploitation context
Not listed in CISA KEV. A public proof-of-concept has been available on ExploitDB (44877) since 2018, and VulnCheck tracks the advisory, so exploitation tooling is trivially accessible. No source in the bundle confirms active in-the-wild exploitation, but the low attack complexity and unauthenticated network vector make opportunistic abuse plausible.
Researcher notes
The CVE record credits harmistechnology's EkRishta 2.10 and CWE-89 with an error-based SQLi in the username POST parameter. The ExploitDB entry (44877) predates the CVE assignment by several years, suggesting the flaw is well-known in offensive tooling. No fixed version is named in the provided sources; validate against the vendor site directly. No CPE list was provided, so scanner coverage may be uneven — hunt by extension name and file fingerprints rather than relying solely on CPE-based detection.
Mitigation direction
Inventory Joomla sites for the EkRishta component and identify any running version 2.10.
Consult the vendor (harmistechnology / joomlaextensions.co.in) for a patched release or written guidance.
If no fix is available, disable or uninstall the EkRishta component until a vendor patch ships.
Place a WAF rule in front of the login endpoint to block SQL injection patterns on the username parameter.
Restrict administrative and login endpoints by IP allowlist where feasible.
Rotate database and application credentials if compromise cannot be ruled out.
Validation and detection
Enumerate installed Joomla extensions and flag any instance of EkRishta 2.10.
Review web server and application logs for POST requests to the EkRishta login endpoint containing SQL syntax in the username field.
Check database logs for unexpected errors or unusual SELECT/UNION queries originating from the web application user.
Confirm WAF or reverse proxy is inspecting and blocking SQLi payloads on login parameters.
Compare user, session, and audit tables against known-good baselines for signs of data exfiltration.
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.