dbcve.org
Courier Management SystemApplication · Campcodes

CVE-2025-8187

HIGH · 8.8 CVSS v3.1 Published 2025-07-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in Campcodes Courier Management System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /edit_parcel.php. The manipulation of the argument ID leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Campcodes Courier Management System 1.0 at /edit_parcel.php. The ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. This is a critical vulnerability given the high CVSS score and public exploit availability.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in edit_parcel.php. Validate and sanitize the ID parameter input, and apply the principle of least privilege to the database user.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Courier Management SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Campcodes Courier Management System is installed
    Locate the web application files in your web server root directory (commonly /var/www/html, /www, or C:\inetpub\wwwroot). Look for directories containing courier management files or a login page associated with this system.
    Affected if The application directory contains Campcodes Courier Management System files.
  2. Verify the application version is 1.0
    Check for a version file, readme.txt, or the footer/header of the application pages for the version number. Common locations include /includes/version.php, /version.txt, or displayed on the login page.
    Affected if The installed version is exactly 1.0.
  3. Confirm edit_parcel.php exists
    Search for the file edit_parcel.php in the web application directory. This is the vulnerable script mentioned in the CVE.
    Affected if The file /edit_parcel.php exists in the web root.
  4. Inspect the ID parameter handling in edit_parcel.php
    Open edit_parcel.php in a text editor and locate where the ID parameter is processed. Search for $_GET['id'] or $_POST['id'] usage. Check if the ID value is directly concatenated into SQL queries without sanitization functions (such as mysqli_real_escape_string, prepared statements, or parameter binding).
    Affected if The ID parameter is used in SQL queries without proper sanitization or parameterized queries.
  5. Check if the application database is accessible
    Verify the database connection configuration in the application's configuration files (such as config.php, db.php, or similar). Ensure the database is accessible over the network or locally.
    Affected if The application connects to a MySQL or other SQL database.

If you have Campcodes Courier Management System version 1.0 with edit_parcel.php present and the ID parameter is processed without sanitization in SQL queries, the system is vulnerable to SQL injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in edit_parcel.php. Validate and sanitize the ID parameter input, and apply the principle of least privilege to the database user.

Fix this in Courier Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8187 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8187 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data