Security readout for executives and security teams
Plain-English summary
Tina4 Stack 1.0.3 has two serious issues: unauthenticated access to a database file and SQL injection in a menu endpoint. A remote attacker may obtain credentials or password hashes and alter database queries. This is high urgency for any internet-facing instance, especially if it stores user accounts or business data.
Executive priority
Treat as urgent if Tina4 Stack 1.0.3 is in use. The main business risk is credential exposure and unauthorized database manipulation without authentication. If no deployments exist, document non-exposure and monitor for vendor guidance.
Technical view
CVE-2018-25187 affects Tina4 Stack 1.0.3. The report describes direct retrieval of the kim.db database file and SQL injection through the menu endpoint. It is mapped to CWE-89 and scored CVSS 4.0 8.8, with network attack vector, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is limited to organizations running Tina4 Stack 1.0.3. Risk is highest when the application is reachable from untrusted networks and the database file is accessible from the web application path.
Exploitation context
The CVE is not listed as CISA KEV in the provided data, so active exploitation is not established. However, a public Exploit-DB reference and a VulnCheck advisory are cited, indicating public technical knowledge exists.
Researcher notes
Evidence is based on the CVE record, VulnCheck advisory, and Exploit-DB reference. The provided sources do not name an official patch level. Avoid assuming broader Tina4 versions are affected unless vendor or CVE data confirms it.
Mitigation direction
- Identify and prioritize any Tina4 Stack 1.0.3 deployments.
- Check Tina4 or trusted advisories for upgrade or vendor remediation guidance.
- Restrict internet access to affected applications until remediated.
- Ensure database files are not web-accessible.
- Rotate credentials if kim.db may have been exposed.
Validation and detection
- Confirm whether Tina4 Stack 1.0.3 is installed.
- Review web directories for exposed kim.db files.
- Test exposure only through authorized, non-destructive checks.
- Review access logs for requests to kim.db.
- Review logs for suspicious menu endpoint activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
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.
Open ATT&CK lookupCVE-2018-25187 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-45833CVE reference · exploit
- VulnCheck Advisory: Tina4 Stack 1.0.3 SQL Injection and Database File DownloadCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.