Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

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

0
Medium
VulnerabilityCVE-2025-13303cvecve-2025-13303
Published: Mon Nov 17 2025 (11/17/2025, 22:02:08 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: Courier Management System

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.

AI-Powered Analysis

AILast updated: 11/24/2025, 23:15:37 UTC

Technical Analysis

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.

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

Mitigation Recommendations

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.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-11-17T14:10:13.358Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 691ba1c4bb922d22627154ce

Added to database: 11/17/2025, 10:29:24 PM

Last enriched: 11/24/2025, 11:15:37 PM

Last updated: 1/7/2026, 10:22:13 AM

Views: 51

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats