VulnerabilityPublished 15 Dec 2025

CVE-2023-36338: SQL Injection

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the absence of official patches, European organizations should immediately implement the following mitigations: 1) Conduct a thorough code review of the Inventory Management System 1 to identify and remediate all instances of unsanitized SQL input, replacing vulnerable queries with parameterized prepared statements or stored procedures. 2) Employ web application firewalls (WAFs) configured to detect and block SQL injection patterns targeting the affected system. 3) Restrict network access to the inventory management system to trusted internal IP ranges and VPN connections only, minimizing exposure to external attackers. 4) Monitor database logs and application logs for unusual query patterns indicative of injection attempts. 5) Educate development and operations teams on secure coding practices to prevent future injection flaws. 6) Engage with the vendor or software maintainer to obtain patches or updates as soon as they become available. 7) Consider implementing database-level access controls and encryption to limit the impact of any potential data leakage. These targeted actions go beyond generic advice by focusing on immediate containment and long-term remediation tailored to this specific vulnerability.

Description

CVE-2023-36338 is a medium-severity SQL injection vulnerability found in Inventory Management System 1. It allows unauthenticated remote attackers to inject SQL queries due to improper input sanitization. The vulnerability impacts confidentiality but not integrity or availability, and no user interaction or privileges are required. No known exploits are currently reported in the wild, and no patches have been published yet. European organizations using this inventory system may face data leakage risks. Mitigation requires immediate input validation and use of parameterized queries. Countries with significant manufacturing and logistics sectors using this software are at higher risk. The vulnerability’s CVSS score is 5.3, reflecting moderate risk primarily from data exposure. Defenders should prioritize detection of suspicious database queries and restrict external access to the affected system until patched.

Impact

For European organizations, the primary impact of CVE-2023-36338 is unauthorized disclosure of sensitive inventory and business data, which can lead to competitive disadvantage, regulatory penalties under GDPR, and loss of customer trust. Since the vulnerability does not affect data integrity or availability, operational disruption is less likely, but data confidentiality breaches can still have severe consequences. Organizations in sectors such as manufacturing, retail, and logistics that heavily depend on inventory management systems are particularly vulnerable. The absence of authentication requirements increases the risk of remote exploitation from external threat actors. Additionally, the lack of known exploits currently in the wild provides a window for proactive defense, but also means attackers may develop exploits soon after disclosure. The medium severity score suggests that while the threat is not critical, it should not be ignored, especially given the sensitive nature of inventory data and the regulatory environment in Europe.

Summary

CVE-2023-36338 identifies a SQL injection vulnerability in Inventory Management System 1, a software product used for managing inventory data. The vulnerability arises from improper sanitization of user-supplied input that is directly incorporated into SQL queries without adequate escaping or parameterization, classified under CWE-89. This flaw enables remote attackers to execute arbitrary SQL commands on the backend database without requiring authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The impact is limited to confidentiality, meaning attackers could potentially extract sensitive data from the database but cannot modify or delete data or disrupt service availability. The CVSS base score of 5.3 (medium severity) reflects this limited impact and ease of exploitation. No affected versions are explicitly listed, and no patches or known exploits are currently available, which suggests the vulnerability is newly disclosed and may not yet be widely exploited. The vulnerability was reserved in June 2023 and published in December 2025, indicating a delayed disclosure timeline. The lack of patches necessitates immediate mitigation strategies to prevent exploitation. The vulnerability is significant for organizations relying on this inventory system, as SQL injection remains a common and dangerous attack vector that can lead to data breaches and compliance violations.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 22 Dec 2025, 21:54 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats