CVE-2026-26891
SQL Injection in Logistic Hub Parcel Management System v
Publication date: 2026-03-03
Last updated on: 2026-03-04
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oretnom23 | simple_logistic_hub_parcel's_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "The vulnerability is an SQL Injection in the Simple Logistic Hub Parcel's Management System v1.0 by Sourcecodester. It exists in the file `/lhpms/manage_parcel_type.php` specifically in the URL parameter `id`. An attacker can inject malicious SQL code through this parameter to manipulate the backend SQLite database."}, {'type': 'paragraph', 'content': "For example, an attacker can use a payload like `/lhpms/manage_parcel_type.php?id=1' union select 1, sqlite_version(), 3, 4--` to retrieve database information such as the SQLite version. This shows that the system does not properly sanitize or validate input, allowing unauthorized access to sensitive data."}] [1]
How can this vulnerability impact me? :
This SQL Injection vulnerability can lead to unauthorized data leakage from the backend database. An attacker exploiting this flaw can access sensitive information stored in the database, which may include confidential business data or user information.
Such unauthorized access can compromise the integrity and confidentiality of the system, potentially leading to further attacks or data breaches.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This SQL Injection vulnerability can be detected by testing the `id` parameter in the URL `/lhpms/manage_parcel_type.php?id=` for SQL injection payloads.'}, {'type': 'paragraph', 'content': 'A common detection method is to send a crafted request with a payload that attempts to extract database information, such as:'}, {'type': 'list_item', 'content': "Accessing `/lhpms/manage_parcel_type.php?id=1' union select 1, sqlite_version(), 3, 4--` to check if the SQLite version is returned, indicating a successful SQL injection."}, {'type': 'paragraph', 'content': 'This can be done using tools like curl or a web browser to observe if the response contains database information or errors indicating SQL injection.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user inputs, especially the `id` parameter in `/lhpms/manage_parcel_type.php`.
Use prepared statements or parameterized queries in the PHP code to prevent SQL injection.
Restrict database permissions to limit the impact of any potential injection.
If possible, apply any available patches or updates from the vendor or source code provider.
Additionally, monitor logs for suspicious requests targeting the `id` parameter.