Skip to content

Product

carmelo simple pizza ordering system vulnerabilities

18 published CVES affecting carmelo simple pizza ordering system, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
18
Critical
0
High
0
Medium
18
Low
0
Unscored
0
CISA KEV
0

Latest carmelo simple pizza ordering system CVEs

Newest publication first

  1. MediumCVSS 6.9 EPSS 0.50%

    A vulnerability was found in code-projects Simple Pizza Ordering System 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /large.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exp...

  2. MediumCVSS 6.9 EPSS 0.50%

    A vulnerability was found in code-projects Simple Pizza Ordering System 1.0. It has been classified as critical. This affects an unknown part of the file /addpro.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The e...

  3. MediumCVSS 6.9 EPSS 0.48%

    A vulnerability, which was classified as critical, has been found in code-projects Simple Pizza Ordering System 1.0. This issue affects some unknown processing of the file /update.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotel...

  4. MediumCVSS 6.9 EPSS 0.53%

    A vulnerability classified as critical has been found in code-projects Simple Pizza Ordering System 1.0. This affects an unknown part of the file /portal.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit h...

  5. MediumCVSS 6.9 EPSS 0.53%

    A vulnerability was found in code-projects Simple Pizza Ordering System 1.0 and classified as critical. This issue affects some unknown processing of the file /addmem.php. The manipulation leads to sql injection. The attack may be initiated remotely. The exploit has been disclose...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.