CVE-2025-13396VulnerabilityPublished 19 Nov 2025

CVE-2025-13396: 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 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 19 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

Organizations should immediately audit their use of the code-projects Courier Management System and confirm if version 1.0 is in use. If so, they should implement strict input validation and sanitization on the OfficeName parameter to prevent SQL injection. Employing parameterized queries or prepared statements in the /add-office.php script is critical to eliminate injection vectors. Monitoring and logging database queries for anomalous activity can help detect exploitation attempts early. If vendor patches or updates become available, they should be applied promptly. Network-level protections such as web application firewalls (WAFs) can be configured to block malicious SQL payloads targeting this endpoint. Additionally, restricting access to the management interface to trusted IPs or VPNs can reduce exposure. Regular security assessments and penetration testing should be conducted to ensure no other injection points exist. Finally, organizations should review their incident response plans to handle potential data breaches stemming from this vulnerability.

Description

A weakness has been identified in code-projects Courier Management System 1.0. This affects an unknown function of the file /add-office.php. This manipulation of the argument OfficeName causes sql injection. The attack may be initiated remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, this vulnerability poses risks to the confidentiality and integrity of courier management data, including office locations, operational details, and potentially customer information. Exploitation could disrupt courier operations by altering or deleting critical data, leading to service delays or failures. Data breaches resulting from SQL injection could also lead to regulatory non-compliance under GDPR, resulting in financial penalties and reputational damage. Organizations in logistics, delivery services, and supply chain management that use the affected Courier Management System version 1.0 are particularly vulnerable. The medium severity rating suggests that while the threat is serious, it may not lead to full system compromise but could still cause significant operational and data security issues. The availability of public exploit code increases the likelihood of opportunistic attacks, especially from automated scanning tools targeting known vulnerabilities.

Summary

CVE-2025-13396 identifies an SQL injection vulnerability in the code-projects Courier Management System version 1.0. The flaw exists in the /add-office.php script, where the OfficeName parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection can be performed remotely without authentication or user interaction, making it accessible to a wide range of attackers. The vulnerability can lead to unauthorized access to the backend database, enabling attackers to read, modify, or delete sensitive courier management data. The CVSS 4.0 base score of 5.3 reflects a medium severity, considering the attack vector is network-based with low complexity and no privileges or user interaction required. However, the impact on confidentiality, integrity, and availability is limited to low, indicating partial compromise rather than full system takeover. No official patches have been linked yet, but the presence of public exploit code increases the risk of exploitation. The vulnerability is significant for organizations relying on this system for managing courier offices, as it could expose operational data and customer information to attackers.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Nov 2025, 16:03 UTC

Technical details

References

Community reviews

Related threats