LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43355: 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 /php-sms/classes/Master.php?f=delete_service.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE is a high-severity SQL injection in Sanitization Management System v1.0. A privileged remote attacker could abuse the vulnerable id parameter to affect database confidentiality, integrity, and availability. The source bundle does not identify a vendor patch or active exploitation.

Executive priority

Treat as a priority if the application exists in production or handles sensitive operational data. The privilege requirement lowers broad internet risk, but successful abuse could compromise the database and disrupt service records.

Technical view

CVE-2022-43355 is CWE-89 SQL injection in /php-sms/classes/Master.php?f=delete_service via the id parameter. CVSS 3.1 is 7.2: network attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and high C/I/A impact.

Likely exposure

Exposure is most likely where Sanitization Management System v1.0 is deployed, especially if the PHP application is reachable over a network. Structured affected metadata lists vendor/product as n/a, so asset owners must verify by application name, path, and codebase.

Exploitation context

The CVE is not listed as KEV in the provided bundle. A public GitHub reference is cited, but the bundle provides no evidence of active exploitation, no exploit prevalence, and no confirmed vendor advisory or patch status.

Researcher notes

Evidence is narrow: the CVE identifies the endpoint, parameter, weakness class, and CVSS vector, but not a vendor CPE, patch, or exploitation status. Validate against actual code before declaring exposure or closure.

Mitigation direction

  • Identify any Sanitization Management System v1.0 deployments.
  • Check the project or vendor source for patch guidance.
  • Restrict access to the application and sensitive service-management functions.
  • If maintaining code, review the handler for parameterized database queries.
  • Back up and monitor the application database before remediation.

Validation and detection

  • Confirm whether /php-sms/classes/Master.php exists in deployed code.
  • Verify whether f=delete_service processes an id parameter.
  • Review code for unsafe SQL construction using id.
  • Check logs for suspicious delete_service requests.
  • Confirm access controls require high privileges for the affected function.
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-43355 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-43355Attack 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.