LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43086: Restaurant POS System v1.0 was discovered to contain a SQL injection vulnerability via update_customer.php.

Restaurant POS System v1.0 was discovered to contain a SQL injection vulnerability via update_customer.php.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-43086 is a SQL injection issue in Restaurant POS System v1.0 affecting update_customer.php. A highly privileged authenticated user could potentially cause unauthorized database reads. The published CVSS score is medium, mainly because exploitation requires high privileges, but confidentiality impact is rated high.

Executive priority

Treat as a targeted remediation item, not an emergency-wide response. Prioritize if the application is internet-accessible, handles sensitive customer data, or is used by many privileged staff. Evidence for active exploitation is not provided.

Technical view

The CVE describes CWE-89 SQL injection in update_customer.php for Restaurant POS System v1.0. CVSS 3.1 is 4.9: network reachable, low complexity, high privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure appears limited to deployments of Restaurant POS System v1.0 where update_customer.php is reachable to privileged users. The CVE metadata lists vendor and product as n/a, so asset identification may require filename, application branding, or repository-based verification.

Exploitation context

The source bundle does not show CISA KEV listing or active in-the-wild exploitation. A public GitHub reference is listed, but the provided evidence does not establish exploitation beyond disclosure of the vulnerability.

Researcher notes

The record is sparse: affected vendor/product fields are n/a, and only the title identifies Restaurant POS System v1.0. The CVSS vector implies authenticated high-privilege exploitation with confidentiality impact only. Avoid assuming broader product lines or patched versions without vendor confirmation.

Mitigation direction

  • Check maintainer or vendor guidance for any fixed release or patch.
  • Restrict access to customer update functionality to trusted administrative users.
  • If maintaining the code, replace dynamic SQL with parameterized queries.
  • Apply least-privilege database permissions for the POS application account.
  • Monitor database and application logs for unusual customer update activity.

Validation and detection

  • Confirm whether Restaurant POS System v1.0 is deployed anywhere.
  • Check whether update_customer.php exists and is reachable.
  • Review update_customer.php for parameterized database access.
  • Verify administrative access is limited to authorized users only.
  • Review logs for suspicious customer update requests or SQL errors.
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-43086 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
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

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
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2022-43086Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

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.