CVE-2025-13234VulnerabilityPublished 16 Nov 2025Updated 7 Jan 2026

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

Affects itsourcecode Inventory Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 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:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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
GitHubpip-in-head/lulucat-VD`pkg:github/pip-in-head/lulucat-VD`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately audit their use of the itsourcecode Inventory Management System version 1.0 and restrict external access to the /index.php?q=product endpoint via network controls such as firewalls or web application firewalls (WAFs). Implement strict input validation and sanitization on the PROID parameter to block malicious SQL payloads. Where possible, refactor the application code to use parameterized queries or prepared statements to eliminate injection risks. Monitor logs for suspicious query patterns or unexpected database errors indicative of exploitation attempts. Engage with the vendor for patches or updates and apply them promptly once available. Conduct penetration testing focused on SQL injection vectors to identify residual vulnerabilities. Additionally, implement database access controls and encryption to limit damage in case of compromise. Educate developers on secure coding practices to prevent similar vulnerabilities in future releases.

Description

A vulnerability was found in itsourcecode Inventory Management System 1.0. The impacted element is an unknown function of the file /index.php?q=product. Performing manipulation of the argument PROID results in sql injection. It is possible to initiate the attack remotely. The exploit has been made public and could be used.

Impact

For European organizations, this vulnerability poses risks primarily to the confidentiality and integrity of inventory data, which can disrupt supply chain operations, financial reporting, and asset management. Attackers exploiting this flaw could gain unauthorized access to sensitive business information, manipulate inventory records, or cause denial of service by corrupting database entries. Industries such as manufacturing, retail, logistics, and wholesale that rely on the itsourcecode Inventory Management System could face operational disruptions and reputational damage. The medium severity score reflects a moderate but tangible threat, especially if combined with other vulnerabilities or insider threats. Given the remote exploitability without authentication, attackers can launch attacks from outside the network, increasing exposure. European organizations with limited cybersecurity maturity or lacking timely patch management are particularly vulnerable.

Summary

CVE-2025-13234 identifies a SQL injection vulnerability in itsourcecode Inventory Management System version 1.0. The vulnerability arises from improper sanitization of the PROID parameter in the /index.php?q=product endpoint, which allows attackers to inject malicious SQL code remotely without requiring authentication or user interaction. This injection flaw can be exploited to manipulate backend database queries, potentially enabling unauthorized data access, data modification, or deletion. The vulnerability has a CVSS 4.0 base score of 5.3, indicating medium severity, with attack vector being network-based and low complexity, but requiring low privileges. The impact on confidentiality, integrity, and availability is limited but non-negligible, as attackers could extract sensitive inventory data or corrupt records. No official patches have been released yet, and while exploit code is publicly available, no confirmed active exploitation has been reported. The vulnerability highlights the critical need for secure coding practices such as input validation and use of parameterized queries in web applications handling inventory data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jan 2026, 19:40 UTC

Technical details

References

Community reviews

Related threats