LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43052: Online Diagnostic Lab Management System v1.0 was discovered to contain a SQL injection vulnerability via th...

Online Diagnostic Lab Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /odlms/classes/Users.php?f=delete.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-43052 is a high-severity SQL injection issue in Online Diagnostic Lab Management System v1.0. A highly privileged user could abuse the delete-user request path to affect database confidentiality, integrity, and availability. The provided sources do not identify a vendor patch or confirm active exploitation.

Executive priority

Treat as high priority if this lab-management system is deployed, internet reachable, or handles regulated patient or diagnostic data. If not deployed, record as not applicable and monitor vendor/project updates.

Technical view

The CVE describes CWE-89 SQL injection in the id parameter of /odlms/classes/Users.php?f=delete. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, and high impact to confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to organizations running Online Diagnostic Lab Management System v1.0, especially deployments where the affected user-management endpoint is reachable by administrator-level accounts. The source metadata does not provide CPEs, vendor ownership, deployment prevalence, or fixed versions.

Exploitation context

The source bundle includes a public GitHub reference but no CISA KEV listing and no cited evidence of exploitation in the wild. Because exploitation requires high privileges, risk is highest after administrator account compromise or insider misuse.

Researcher notes

Affected metadata is sparse: vendor, CPEs, and fixed versions are listed as unavailable. Analysis should stay tied to the named application, version 1.0, endpoint, CVSS vector, CWE-89 classification, and the single public GitHub reference.

Mitigation direction

  • Check the project or vendor for patched versions or official guidance.
  • Restrict access to administrative user-management functions to trusted networks and roles.
  • Review the affected code path for parameterized database queries.
  • Monitor administrative delete-user requests and database errors for anomalies.
  • Reduce standing administrator privileges where operationally possible.

Validation and detection

  • Inventory any Online Diagnostic Lab Management System v1.0 deployments.
  • Confirm whether /odlms/classes/Users.php?f=delete exists and is reachable.
  • Review source code handling of the id parameter for unsafe SQL construction.
  • Check access logs for unusual administrative delete-user activity.
  • Document whether a vendor fix or local code remediation has been applied.
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-2022-43052 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-43052Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
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.