CVE-2025-13233VulnerabilityPublished 16 Nov 2025Updated 17 Nov 2025

CVE-2025-13233: itsourcecode Inventory Management System · SQL Injection

Affects itsourcecode Inventory Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Nov 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 2026-10-25.

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 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

Affected software

Product	Affected	Fixed in
itsourcecode Inventory Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate implementation of input validation and sanitization on the 'ID' parameter in the /index.php?q=single-item endpoint to prevent injection of malicious SQL code. 2. Refactor the application code to use parameterized queries or prepared statements to eliminate direct concatenation of user input into SQL commands. 3. Restrict network access to the inventory management system by implementing firewall rules or VPN access to limit exposure to trusted users only. 4. Monitor application logs for unusual query patterns or repeated failed attempts that may indicate exploitation attempts. 5. If possible, isolate the database with strict access controls and least privilege principles to minimize damage in case of compromise. 6. Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available. 7. Conduct regular security assessments and penetration testing focused on injection flaws to proactively identify and remediate similar issues. 8. Educate developers on secure coding practices to prevent future injection vulnerabilities.

Description

A vulnerability has been found in itsourcecode Inventory Management System 1.0. The affected element is an unknown function of the file /index.php?q=single-item. Such manipulation of the argument ID leads to sql injection. The attack may be performed from remote. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using itsourcecode Inventory Management System 1.0, this vulnerability poses a significant risk to the confidentiality and integrity of inventory data, which may include sensitive business information, supplier details, and stock levels. Exploitation could disrupt supply chain operations, cause financial losses, and damage organizational reputation. In sectors such as manufacturing, retail, and logistics, where inventory management is critical, successful attacks could lead to operational downtime or erroneous inventory reporting. Additionally, compromised inventory systems could serve as pivot points for attackers to infiltrate broader corporate networks. Given the remote exploitability without authentication, attackers can target exposed systems over the internet, increasing the threat surface. The medium severity rating suggests moderate impact, but the actual damage depends on the deployment context and data sensitivity.

Summary

CVE-2025-13233 is a SQL Injection vulnerability identified in the itsourcecode Inventory Management System version 1.0, specifically in the /index.php?q=single-item endpoint. The vulnerability arises due to improper sanitization of the 'ID' parameter, which allows an attacker to inject arbitrary SQL commands remotely without requiring authentication or user interaction. This can lead to unauthorized data access, modification, or deletion within the backend database, potentially compromising confidentiality, integrity, and availability of stored information. The vulnerability has been publicly disclosed, though no known exploits are currently active in the wild. The CVSS 4.0 score of 6.9 indicates a medium severity level, with an attack vector over the network, low attack complexity, and no privileges or user interaction required. The scope is limited to the vulnerable version 1.0 of the software. The lack of patch links suggests that a fix may not yet be available, increasing the urgency for organizations to implement mitigations. SQL Injection vulnerabilities are critical because they can be leveraged to escalate attacks, including data exfiltration, privilege escalation, or even full system compromise depending on the backend database and application architecture.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Nov 2025, 04:51 UTC

Technical details

References

Community reviews

Related threats