LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19221: An issue was discovered in LAOBANCMS 2.0.

An issue was discovered in LAOBANCMS 2.0. It allows SQL Injection via the admin/login.php guanliyuan parameter.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-19221 is a reported SQL injection issue in LAOBANCMS 2.0 affecting the admin login flow. If exploitable, it could let an attacker interfere with database-backed authentication or data handling. The public record does not provide CVSS scoring, confirmed affected CPEs, or vendor remediation details.

Executive priority

Prioritize inventory first. Escalate quickly if LAOBANCMS 2.0 is internet-facing or business-critical, because SQL injection in an admin login path can create serious data and access risk despite missing severity scoring.

Technical view

The CVE description states LAOBANCMS 2.0 allows SQL injection through the guanliyuan parameter in admin/login.php. The available source bundle identifies one external proof reference but does not include a vendor advisory, patch version, CVSS vector, CWE mapping, or confirmed exploitation evidence.

Likely exposure

Exposure appears limited to deployments of LAOBANCMS 2.0, particularly where the admin/login.php endpoint is reachable from untrusted networks. The CVE record does not list formal CPEs or broader affected versions.

Exploitation context

The provided sources do not establish active exploitation. The KEV flag is false, and the bundle only cites a public GitHub reference for the SQL injection claim. Treat exploitability as plausible but not independently quantified from the supplied evidence.

Researcher notes

Evidence is sparse: the CVE names the vulnerable parameter and path, but lacks CVSS, CWE, CPEs, patch metadata, and exploitation confirmation. Validation should focus on confirming product presence, endpoint exposure, and whether maintained upstream guidance exists.

Mitigation direction

  • Inventory whether LAOBANCMS 2.0 is deployed anywhere in the environment.
  • Restrict access to admin/login.php to trusted administrative networks.
  • Check the LAOBANCMS project or vendor guidance for a fixed release.
  • Retire or isolate unsupported installations if no maintained fix is available.
  • Review database and admin authentication logs for unusual activity.

Validation and detection

  • Confirm whether any internet-facing service identifies as LAOBANCMS 2.0.
  • Verify whether admin/login.php is reachable by unauthenticated users.
  • Check source or package history for input handling around guanliyuan.
  • Review change logs or vendor notes for SQL injection fixes.
  • Document compensating controls if patch status cannot be confirmed.
Prepared
Confidence
medium
Sources
3

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.

description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2018-19221 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.