LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43081: Fast Food Ordering System v1.0 was discovered to contain a SQL injection vulnerability via the component /f...

Fast Food Ordering System v1.0 was discovered to contain a SQL injection vulnerability via the component /fastfood/purchase.php.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes a SQL injection issue in Fast Food Ordering System v1.0, specifically the purchase.php component. An unauthenticated network attacker may be able to access sensitive database information. The source bundle does not name a vendor, CPE, patch, or confirmed exploitation.

Executive priority

Treat this as a high-priority exposure review if the organization runs this application. The main business risk is unauthorized database disclosure from a public ordering workflow. Urgency depends on whether the named application is deployed and internet-facing.

Technical view

CVE-2022-43081 is mapped to CWE-89. CVSS 3.1 is 7.5 high, with network attack vector, low complexity, no privileges, and no user interaction. Impact is confidentiality high, with integrity and availability not scored. The vulnerable component is listed as /fastfood/purchase.php.

Likely exposure

Exposure is most likely on internet-accessible deployments of Fast Food Ordering System v1.0 that expose /fastfood/purchase.php. Discovery may be difficult because the CVE record lists affected vendor, product, versions, and CPEs as n/a.

Exploitation context

The bundle does not show CISA KEV inclusion or other evidence of active exploitation. A public GitHub reference is listed, so technical details may be publicly available, but exploitation in the wild is not established by the provided sources.

Researcher notes

The CVE metadata is sparse: no vendor, CPE, fixed version, or official remediation is provided in the bundle. Validation should focus on confirming actual deployment, reachability of the named component, and whether database queries are parameterized.

Mitigation direction

  • Identify any deployments of Fast Food Ordering System v1.0.
  • Restrict public access to affected purchase functionality where feasible.
  • Check vendor or project guidance for a fixed release or advisory.
  • Review purchase.php database access for parameterized queries and input handling.
  • If no fix exists, isolate, replace, or retire the application.

Validation and detection

  • Inventory public web apps for Fast Food Ordering System v1.0.
  • Confirm whether /fastfood/purchase.php is reachable.
  • Review purchase handling code for unsafe SQL construction.
  • Run authorized, non-destructive SQL injection checks.
  • Review logs for unusual purchase.php requests or database 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-43081 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-43081Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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.