CVE-2018-25382: Zechat 1.5 SQL Injection via uname Parameter
Zechat 1.5 contains an SQL injection vulnerability that allows unauthenticated attackers to extract database information by injecting SQL code through the uname parameter. Attackers can send crafted requests to profile.php with UNION-based SQL injection payloads to retrieve table names, column names, and sensitive data from the information_schema database.
Security readout for executives and security teams
Plain-English summary
Zechat 1.5 has an unauthenticated SQL injection flaw that can expose database information. The issue affects a web chat product, so any internet-facing deployment is the main business concern. Public exploit material exists, but the supplied sources do not show confirmed active exploitation or a vendor patch.
Executive priority
Treat this as a high-priority internet-facing application risk. The main concern is database confidentiality, with public exploit material available and no patch named in the supplied sources.
Technical view
CVE-2018-25382 is CWE-89 SQL injection in Bylancer Zechat 1.5 through the uname parameter associated with profile.php. The CVSS 4.0 score is 8.8, reflecting network reachability, low attack complexity, no privileges, no user interaction, and high confidentiality impact.
Likely exposure
Organizations are exposed if they run Bylancer Zechat 1.5, especially on public web servers. The bundle does not identify other affected versions, CPEs, hosted services, or downstream products.
Exploitation context
The CVE is not listed as KEV in the supplied bundle. ExploitDB is cited as public exploit material, so defenders should assume attackers can understand the weakness. No cited source confirms real-world active exploitation.
Researcher notes
Evidence is limited to Zechat 1.5 and the uname parameter. Do not generalize to other versions without vendor or advisory confirmation. Avoid destructive testing; use inventory, version checks, logs, and approved validation methods.
Mitigation direction
Identify and prioritize any Zechat 1.5 deployments.
Check Bylancer and VulnCheck guidance for supported remediation.
Remove or disable Zechat 1.5 if no supported fix exists.
Restrict public access to affected Zechat functionality pending remediation.
Monitor web logs for SQL injection patterns targeting Zechat routes.
Validation and detection
Confirm whether Zechat 1.5 exists in asset inventory or web roots.
Review application version evidence before marking assets affected.
Check web logs for suspicious requests involving the uname parameter.
Validate exposure from the internet and trusted networks separately.
Document any compensating controls and remaining public access.
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.