CVE-2025-13303VulnerabilityPublished 17 Nov 2025

CVE-2025-13303: code-projects Courier Management System · SQL Injection

Affects code-projects Courier 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 33% 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 17 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
code-projects Courier Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-13303, organizations should immediately implement input validation and sanitize the 'Consignment' parameter in the /search-edit.php file to prevent SQL injection. Employing parameterized queries or prepared statements is critical to eliminate injection vectors. If source code modification is not immediately feasible, deploying a Web Application Firewall (WAF) with custom rules to detect and block SQL injection patterns targeting the vulnerable endpoint can reduce risk. Restricting access to the /search-edit.php endpoint via network segmentation or IP whitelisting limits exposure. Monitoring database logs and application logs for suspicious queries or anomalies can help detect exploitation attempts early. Organizations should also engage with the vendor or community to obtain patches or updates and plan for timely application once available. Conducting security assessments and penetration tests focused on injection flaws in the courier management system is advisable. Finally, ensure that backups of critical data are maintained and tested to enable recovery in case of data corruption or loss.

Description

A vulnerability was determined in code-projects Courier Management System 1.0. Affected by this issue is some unknown functionality of the file /search-edit.php. This manipulation of the argument Consignment causes sql injection. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The SQL injection vulnerability in the Courier Management System can lead to unauthorized access to sensitive shipment and customer data, potentially exposing personally identifiable information and business-critical logistics details. Attackers could manipulate database queries to alter or delete records, impacting data integrity and operational continuity. For European organizations, this could result in regulatory non-compliance, especially under GDPR, due to data breaches involving personal data. Disruption of courier operations may also affect supply chains, causing financial losses and reputational damage. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, particularly targeting logistics companies that rely on this software for managing consignments. The medium severity score reflects moderate but tangible risks to confidentiality, integrity, and availability. Without mitigation, attackers could leverage this vulnerability to gain footholds within corporate networks or exfiltrate sensitive data, making it a significant concern for European logistics and courier service providers.

Summary

CVE-2025-13303 identifies a SQL injection vulnerability in version 1.0 of the code-projects Courier Management System, specifically within the /search-edit.php file. The vulnerability arises from improper sanitization of the 'Consignment' parameter, which can be manipulated by an attacker to inject arbitrary SQL commands. This injection flaw allows remote attackers to execute unauthorized database queries without requiring authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/AT:N/UI:N/PR:L). The vulnerability impacts confidentiality, integrity, and availability at a low level, as attackers could potentially read or modify data and disrupt service. The CVSS 4.0 base score is 5.3, categorizing it as medium severity. Although no known exploits are currently active in the wild, the public disclosure of the vulnerability increases the risk of exploitation by threat actors. The affected product is used in courier and logistics management, making it a target for attackers seeking to access shipment data or disrupt operations. The lack of available patches necessitates immediate mitigation through secure coding practices such as parameterized queries and input validation. Additionally, monitoring and restricting access to the vulnerable endpoint can reduce exposure. This vulnerability highlights the importance of secure software development and timely vulnerability management in logistics software.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Nov 2025, 23:15 UTC

Technical details

References

Community reviews

Related threats