LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43353: Sanitization Management System v1.0 was discovered to contain a SQL injection vulnerability via the id para...

Sanitization Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /admin/?page=orders/view_order.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-43353 is a high-severity SQL injection in Sanitization Management System v1.0. A privileged user could abuse the admin order-view function to affect database confidentiality, integrity, and availability. The source bundle does not identify a vendor patch or fixed version.

Executive priority

Treat this as high priority if the application is in production or stores sensitive customer, order, or operational data. Prioritize inventory first because official affected-product metadata is incomplete.

Technical view

The issue is CWE-89 SQL injection via the id parameter at /admin/?page=orders/view_order. CVSS 3.1 is 7.2 with network access, low complexity, high privileges required, no user interaction, and high impact to confidentiality, integrity, and availability.

Likely exposure

Exposure appears limited to deployments of Sanitization Management System v1.0 where the admin route is reachable. The CVE record lists vendor, product, CPE, and affected version metadata as n/a, so automated asset matching may be incomplete.

Exploitation context

The bundle includes a public GitHub vulnerability report, but no KEV listing and no cited evidence of active exploitation. Because privileges are required, risk depends heavily on admin account security, admin-panel exposure, and database sensitivity.

Researcher notes

The main uncertainty is product provenance and patch availability. The CVSS vector requires high privileges, so validation should focus on authenticated admin attack surface, SQL query construction, logging evidence, and compensating access controls.

Mitigation direction

  • Check vendor or project guidance for any patch or maintained replacement.
  • Restrict access to the admin interface to trusted networks or VPN.
  • Review the vulnerable route for parameterized database queries.
  • Rotate privileged credentials if suspicious admin activity is found.
  • Back up affected databases before applying remediation changes.

Validation and detection

  • Inventory systems for Sanitization Management System v1.0 deployments.
  • Confirm whether /admin/?page=orders/view_order exists and requires privileged access.
  • Review code handling of the id parameter for unsafe SQL construction.
  • Check admin access logs for unusual order-view requests.
  • Use authenticated, non-production testing to verify remediation safely.
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-43353 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-43353Attack 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.