Security readout for executives and security teams
Plain-English summary
CVE-2017-20127 is a SQL injection issue in KB Login Authentication Script 1.1. A remote unauthenticated attacker may manipulate login credentials and affect confidentiality, integrity, and availability. Public exploit disclosure exists, so exposed legacy deployments deserve prompt attention. The provided sources do not show CISA KEV listing or confirmed active exploitation.
Executive priority
Treat as high priority for any confirmed deployment because exploitation is remote, unauthenticated, and publicly documented. Business urgency depends on whether the old script is still reachable and what data or administrative access sits behind it.
Technical view
The issue is classified as CWE-89 with CVSS 3.1 score 7.3: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. The username and password inputs are implicated, but the affected function is unspecified. Sources describe remote exploitability and public exploit disclosure, but do not provide vendor patch details.
Likely exposure
Exposure is limited to deployments of KB Login Authentication Script 1.1, especially internet-facing login pages. The bundle provides no CPEs, vendor name, asset-discovery fingerprints, or evidence that later versions exist.
Exploitation context
Sources state an exploit has been publicly disclosed and may be used. The CVE is not flagged as KEV in the provided bundle, so active exploitation should not be asserted from this evidence alone.
Researcher notes
The public record is thin: product version 1.1 is named, but vendor, CPE, exact component, patch status, and exploit-in-the-wild evidence are absent. Focus research on asset confirmation, code provenance, and whether local forks reused the vulnerable authentication logic.
Mitigation direction
- Inventory sites for KB Login Authentication Script 1.1 or derivative login code.
- Remove or replace exposed affected deployments where feasible.
- Check the vendor or maintainer for current remediation guidance.
- Restrict access to affected login pages until remediation is complete.
- Review application logs for suspicious login and database error activity.
Validation and detection
- Confirm whether any asset runs KB Login Authentication Script 1.1.
- Map affected login pages to owners, hosting locations, and data stores.
- Verify whether public access to affected pages is required.
- Review logs for unusual authentication attempts or SQL error patterns.
- Document remediation status and compensating controls for each exposed instance.
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-2017-20127 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
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://www.exploit-db.com/exploits/41167/CVE reference · x_refsource_MISC
- https://vuldb.com/?id.96620CVE reference · x_refsource_MISC
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.