LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43331: Canteen Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter...

Canteen Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /php_action/printOrder.php.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-43331 is a SQL injection issue in Canteen Management System v1.0. A high-privileged attacker could manipulate the order-printing request and potentially read or change database data. The public data does not identify a fixed release or confirm active exploitation.

Executive priority

Treat this as a high-priority application risk where the system is deployed. It requires high privileges, which reduces broad internet-drive-by risk, but successful abuse could affect sensitive data and database integrity.

Technical view

The vulnerability is CWE-89 SQL injection through the id parameter at /php_action/printOrder.php. CVSS 3.1 is 7.2 with network access, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely limited to organizations running Canteen Management System v1.0 with the printOrder.php route reachable to high-privileged users. Vendor, CPE, and package identifiers are not provided, so asset matching may require manual application inventory.

Exploitation context

The CVE is not listed as KEV in the supplied data, and the bundle provides no evidence of active exploitation. A public bug report exists, so defenders should assume the weakness is discoverable, but avoid claiming exploitation without stronger evidence.

Researcher notes

CVE metadata lacks a named vendor, CPE, and fixed version. The strongest source detail is the endpoint and vulnerable parameter. CVSS indicates PR:H, so validation should include authentication and role assumptions before concluding exposure.

Mitigation direction

  • Check vendor or project guidance for a fixed release or official workaround.
  • Restrict access to /php_action/printOrder.php to required trusted users only.
  • If maintaining the code, use parameterized queries for the id lookup.
  • Apply least-privilege database permissions for the application account.
  • Monitor database and application logs for unusual order-printing requests.

Validation and detection

  • Confirm whether Canteen Management System v1.0 is deployed anywhere.
  • Verify whether /php_action/printOrder.php is present and reachable.
  • Review server-side handling of the id parameter for unsafe SQL construction.
  • Confirm remediation in staging using safe, non-destructive validation tests.
  • Check logs for suspicious access to the affected endpoint.
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-43331 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-43331Attack 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.