CVE-2025-11553VulnerabilityPublished 9 Oct 2025

CVE-2025-11553: 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 9 Oct 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

1. Immediately restrict external access to the /add-courier.php endpoint by implementing network-level controls such as firewalls or VPNs to limit exposure. 2. Apply strict input validation and sanitization on the Shippername parameter to reject or escape malicious SQL characters. 3. Refactor the application code to use parameterized queries or prepared statements to prevent SQL injection. 4. Monitor logs for unusual or suspicious SQL query patterns or repeated access attempts to the vulnerable endpoint. 5. If possible, upgrade to a newer, patched version of the Courier Management System once available from the vendor. 6. Conduct a thorough security review of all input handling in the application to identify and remediate similar vulnerabilities. 7. Implement web application firewalls (WAF) with rules targeting SQL injection attempts to provide an additional layer of defense. 8. Educate IT and security teams about this vulnerability and ensure incident response plans include steps for SQL injection attacks. 9. Regularly back up databases and test restoration procedures to minimize impact in case of data corruption or loss.

Description

CVE-2025-11553 is a medium severity SQL injection vulnerability in code-projects Courier Management System version 1.0, specifically in the /add-courier.php file via the Shippername parameter. The vulnerability allows remote attackers to manipulate SQL queries without authentication or user interaction, potentially compromising confidentiality, integrity, and availability of the backend database. Although no public exploits are currently observed in the wild, proof-of-concept code is available, increasing the risk of exploitation. This threat primarily affects organizations using this specific courier management software, which may include logistics and delivery companies. European organizations relying on this system could face data breaches, unauthorized data manipulation, or service disruption. Mitigation requires immediate input validation, parameterized queries, and software updates or patches once available. Countries with significant logistics sectors and known usage of this software are at higher risk. Given the medium CVSS score and ease of remote exploitation without authentication, organizations should prioritize remediation to prevent potential attacks.

Impact

For European organizations using the affected Courier Management System 1.0, this vulnerability poses risks including unauthorized disclosure of sensitive shipment and customer data, data integrity violations through unauthorized modification of courier records, and potential service disruptions due to database errors or crashes. Logistics and delivery companies are particularly at risk, as they rely heavily on accurate and secure courier management systems. Exposure of shipment data could lead to privacy violations under GDPR, resulting in regulatory fines and reputational damage. Additionally, attackers could leverage the vulnerability to pivot into internal networks if the system is connected to broader enterprise infrastructure. The medium severity score reflects moderate impact, but the ease of remote exploitation without authentication increases urgency. European organizations with internet-facing deployments of this software are especially vulnerable. The absence of known active exploits reduces immediate risk but does not eliminate the threat, as public exploit code availability facilitates potential attacks.

Summary

CVE-2025-11553 identifies a SQL injection vulnerability in the Courier Management System 1.0 developed by code-projects. The vulnerability exists in the /add-courier.php endpoint, where the Shippername parameter is improperly sanitized, allowing an attacker to inject malicious SQL commands. This flaw enables remote attackers to manipulate backend SQL queries without requiring authentication or user interaction, potentially leading to unauthorized data access, data modification, or database corruption. The vulnerability has a CVSS 4.0 base score of 5.3 (medium severity), reflecting its moderate impact and ease of exploitation. Although no confirmed exploits are currently active in the wild, proof-of-concept exploit code has been publicly disclosed, increasing the likelihood of exploitation attempts. The vulnerability affects only version 1.0 of the Courier Management System, which is used to manage courier and shipment data. Exploitation could result in exposure of sensitive customer and shipment data, unauthorized changes to courier records, or denial of service due to database errors. The lack of authentication requirements and remote attack vector make this vulnerability particularly concerning for organizations that have exposed this system to external networks. No official patches or updates have been linked yet, so mitigation currently relies on input validation and restricting access to the vulnerable endpoint.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2025, 05:23 UTC

Technical details

References

Community reviews

Related threats