CVE Intelligence
Medium Injection exploit reference

CVE-2026-114380 — itsourcecode Online Cake Ordering System inserttrans.php sql injection

A vulnerability was found in itsourcecode Online Cake Ordering System 1.0. Impacted is an unknown function of the file /inserttrans.php. Performing a manipulation of the argument prcd results in sql injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used.

Published Oct 21, 2026 · Updated Oct 21, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Itsourcecode
Online Cake Ordering System
CVSS base
6.3
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Itsourcecode Online Cake Ordering System).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Itsourcecode Online Cake Ordering System version 1.0 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
2.1 CVSS 4.0 Low — — cna@vuldb.com via NIST National Vulnerability Database
6.3 CVSS 3.1 Medium 2.8 3.4 cna@vuldb.com via NIST National Vulnerability Database
6.3 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
6.3 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
6.5 CVSS 2.0 Medium 8.0 6.4 cna@vuldb.com via NIST National Vulnerability Database
6.5 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-74 · Injection

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · itsourcecode/online cake ordering system
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 21, 2026
  • CVSS changed · 6.3
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 21, 2026 · Alertas do Telegram
  • CVE published
    Oct 21, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 21, 2026 – Oct 21, 2026
  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

6 on the record

Elsewhere on this site

Itsourcecode
every CVE for this vendor
Injection
same class
CWE-74
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-114384 itsourcecode Online Cake Ordering System transactionsave.php sql injection 7h
  • CVE-2026-114381 itsourcecode Online Cake Ordering System orderdetail.php sql injection 7h
  • CVE-2026-114378 itsourcecode Online Cake Ordering System deleteproduct.php sql injection 8h
  • CVE-2026-113741 itsourcecode Online Cake Ordering System 404.php cross site scripting 1d
  • CVE-2026-113740 itsourcecode Online Cake Ordering System deletecustomer.php sql injection 1d
  • CVE-2026-112087 itsourcecode Online Cake Ordering System confirm.php sql injection 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-114380 is "itsourcecode Online Cake Ordering System inserttrans.php sql injection", rated Medium. It affects Online Cake Ordering System (Itsourcecode); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.