LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2046: SQLi in Yontem Vehicle TrackingSsystem

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Yontem Informatics Vehicle Tracking System allows SQL Injection.This issue affects Vehicle Tracking System: before 8.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Yontem Informatics Vehicle Tracking System before version 8 has a critical SQL injection flaw. An unauthenticated network attacker could potentially read, change, or disrupt backend data if a vulnerable deployment is exposed. Public evidence provided does not confirm active exploitation.

Executive priority

Treat as urgent where the product is deployed. The issue has maximum business impact potential across data confidentiality, integrity, and availability, but urgency depends on whether vulnerable pre-8 systems exist in your environment.

Technical view

CVE-2023-2046 is a CWE-89 SQL injection issue in Yontem Informatics Vehicle Tracking System before 8. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant to organizations running Yontem Informatics Vehicle Tracking System before version 8, especially if reachable from the internet or shared networks. The source bundle does not provide CPEs or deployment prevalence.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source confirms exploitation in the wild. The CVSS vector indicates exploitation may be possible remotely without authentication, but technical details are limited.

Researcher notes

Public data is sparse. The bundle names SQL injection and affected versions before 8, but provides no CPEs, exploit details, endpoint information, or confirmed patch advisory beyond version boundary information.

Mitigation direction

  • Identify any Yontem Vehicle Tracking System deployments and confirm versions.
  • Prioritize remediation for deployments before version 8.
  • Check vendor or USOM guidance before applying operational changes.
  • Restrict network access to trusted users until remediation is confirmed.
  • Increase monitoring for database errors and suspicious application activity.

Validation and detection

  • Confirm product and version with asset owners or vendor records.
  • Check whether the system is internet-facing or broadly reachable.
  • Review logs for unusual SQL errors or unexpected query failures.
  • Verify remediation status against vendor or USOM advisory references.
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.

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.

Open ATT&CK lookup
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-2023-2046 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-2046Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Yontem InformaticsVehicle Tracking System0unaffected
Weakness

CWE details

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.