LiveActive security incident?Get immediate response
CVE Record

CVE-2020-29297: Multiple SQL Injection vulnerabilities in tourist5 Online-food-ordering-system 1.0.

Multiple SQL Injection vulnerabilities in tourist5 Online-food-ordering-system 1.0.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE covers multiple SQL injection flaws in tourist5 Online-food-ordering-system 1.0. A remote unauthenticated attacker could potentially read, change, or disrupt the application database. The CVSS 9.8 rating reflects worst-case impact, but the source bundle does not identify a vendor patch or confirmed exploitation.

Executive priority

Prioritize any internet-facing deployment immediately. The business risk is database compromise, including customer data exposure, order tampering, and service disruption. If the software is not deployed, document non-exposure and monitor only.

Technical view

The issue is classified as CWE-89 SQL injection with CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Public references point to a GitHub issue, repository, and external write-up for the vulnerable project. Affected metadata is incomplete in the CVE record.

Likely exposure

Exposure is likely limited to deployments of tourist5 Online-food-ordering-system 1.0 and closely related forks. The CVE affected-product fields are listed as n/a, so asset matching requires repository, code, package, and application-name review rather than CPE matching.

Exploitation context

The vulnerability is remotely reachable and requires no authentication or user interaction according to the CVSS vector. The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references may help attackers understand the issue, so internet-facing deployments should be treated as urgent.

Researcher notes

The CVE record is sparse: affected vendor/product fields are n/a, and no patch is named in the provided sources. Treat the GitHub project, issue, and CVE List entry as primary scoping evidence. Avoid assuming other food-ordering systems are affected.

Mitigation direction

  • Check the project repository and issue tracker for maintainer guidance or fixes.
  • Remove public exposure until the application is reviewed or remediated.
  • Use parameterized queries for database access if maintaining a fork.
  • Restrict database permissions used by the web application.
  • Add compensating controls such as WAF rules only as temporary protection.

Validation and detection

  • Inventory systems running tourist5 Online-food-ordering-system 1.0 or forks.
  • Review source code for concatenated SQL using request-controlled input.
  • Check application logs for SQL errors or suspicious database query patterns.
  • Confirm whether any local fork has replaced unsafe queries.
  • Verify database accounts follow least privilege.
Prepared
Confidence
medium
Sources
5

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-2020-29297 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
4Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-29297Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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