LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43362: Senayan Library Management System v9.4.2 was discovered to contain a SQL injection vulnerability via the co...

Senayan Library Management System v9.4.2 was discovered to contain a SQL injection vulnerability via the collType parameter at loan_by_class.php.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-43362 is a high-severity SQL injection in Senayan Library Management System v9.4.2. A highly privileged user could potentially affect the application database through the collType parameter in loan_by_class.php. The sources do not show active exploitation or a named patch.

Executive priority

Treat as a prioritized remediation item for any SLiMS v9.4.2 system holding operational or personal data. It is not currently evidenced as exploited, but database compromise impact is high if a privileged account is abused.

Technical view

The CVE describes CWE-89 SQL injection in loan_by_class.php via collType. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Senayan Library Management System v9.4.2 deployments, especially where privileged users can access loan_by_class.php. The CVE record provides no CPEs or normalized vendor/product metadata, so version-based asset inventory is important.

Exploitation context

The provided bundle does not establish active exploitation, and the CVE is not marked KEV. Risk is still meaningful because successful SQL injection could affect sensitive records or database integrity, but exploitation requires high privileges according to CVSS.

Researcher notes

Evidence is sparse: CVE metadata, CVSS vector, CWE-89, and one GitHub issue reference. No official affected CPEs, exploit-in-the-wild evidence, or specific patch version is included in the supplied sources.

Mitigation direction

  • Check SLiMS upstream guidance and issue #163 for fixed versions or official remediation.
  • Upgrade affected v9.4.2 deployments if a vendor-supported fixed release is available.
  • Restrict privileged access to the loan_by_class.php functionality to trusted administrators only.
  • Review database account permissions used by the application for least privilege.
  • Monitor application and database logs for unusual loan_by_class.php or collType activity.

Validation and detection

  • Inventory SLiMS deployments and confirm whether version 9.4.2 is present.
  • Confirm whether loan_by_class.php is reachable in production environments.
  • Verify which roles can access the affected loan-by-class functionality.
  • Review source or vendor patch notes for parameterized handling of collType.
  • Use authorized, non-destructive testing only to validate remediation status.
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-43362 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-43362Attack 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.