CVE-2025-13302VulnerabilityPublished 17 Nov 2025

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

Affects code-projects Courier Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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-26.

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

1. Monitor vendor communications closely and apply security patches immediately once available. 2. Implement strict input validation and sanitization on all user-supplied data, especially parameters like ManagerName. 3. Enforce the principle of least privilege by restricting database user permissions to only what is necessary for application functionality. 4. Conduct regular audits of user accounts and privileges to detect and remove unnecessary high-privilege access. 5. Employ web application firewalls (WAFs) configured to detect and block SQL injection attempts targeting the vulnerable endpoint. 6. Monitor logs for suspicious database queries or unusual activity related to /add-new-officer.php. 7. Educate internal users about the risks of credential compromise and enforce strong authentication mechanisms to reduce insider threat risks. 8. Consider network segmentation to isolate critical systems and limit exposure.

Description

CVE-2025-13302 is a medium-severity SQL injection vulnerability affecting version 1.0 of the code-projects Courier Management System. The flaw exists in the /add-new-officer.php file, where the ManagerName parameter is improperly sanitized, allowing remote attackers to inject malicious SQL commands. Exploitation requires no user interaction but does require high privileges, limiting attack vectors. Although no known exploits are currently in the wild, a public exploit is available, increasing risk. The vulnerability could lead to unauthorized data access or modification, impacting confidentiality, integrity, and availability of the system. European organizations using this software, especially logistics and courier services, could face data breaches or operational disruptions. Mitigation involves applying patches when available, implementing strict input validation, and restricting database user privileges. Countries with significant logistics sectors and adoption of this software, such as Germany, France, and the UK, are most likely to be affected.

Impact

For European organizations, particularly those in the logistics and courier sectors, exploitation of this vulnerability could lead to unauthorized access to employee or operational data, manipulation of records, and potential disruption of courier services. This could result in data breaches involving personal or business-critical information, regulatory non-compliance (e.g., GDPR violations), and reputational damage. Operational disruptions could affect delivery schedules and customer satisfaction. Since the vulnerability requires high privileges, the risk is higher from insider threats or attackers who have already compromised privileged accounts. The availability of a public exploit increases the likelihood of opportunistic attacks if the system remains unpatched. Organizations relying on this software without adequate compensating controls are at increased risk.

Summary

CVE-2025-13302 identifies a SQL injection vulnerability in the Courier Management System version 1.0 developed by code-projects. The vulnerability resides in the /add-new-officer.php script, specifically in the handling of the ManagerName parameter. Due to insufficient input validation or sanitization, an attacker with high privileges can inject arbitrary SQL commands remotely, potentially manipulating the backend database. This could allow unauthorized retrieval, modification, or deletion of sensitive data stored within the system. The vulnerability does not require user interaction but does require the attacker to have elevated privileges, which limits the attack surface to insiders or compromised accounts. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no authentication required (AT:N), but high privileges (PR:H) are necessary. The impact on confidentiality, integrity, and availability is low to medium, reflecting limited scope and privilege requirements. No patches have been published yet, and no known exploits are actively used in the wild, but a public exploit exists, increasing the risk of exploitation. The Courier Management System is typically used by logistics and courier companies to manage personnel and operations, making the data involved sensitive and critical to business continuity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Nov 2025, 22:16 UTC

Technical details

References

Community reviews

Related threats