dbcve.org
Supplier Management SystemApplication · Campcodes

CVE-2025-14877

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 identified in Campcodes Supplier Management System 1.0. This affects an unknown function of the file /admin/add_retailer.php. The manipulation of the argument cmbAreaCode leads to sql injection. The attack is possible to be carried out remotely. The exploit is publicly available and might 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 · moderate confidence

SQL injection vulnerability in Campcodes Supplier Management System 1.0 allows remote attackers to inject malicious SQL code through the cmbAreaCode parameter in /admin/add_retailer.php. The lack of input sanitization enables attackers to manipulate database queries, potentially leading to unauthorized data access or complete system compromise.

MitigationImplement parameterized queries (prepared statements) for all SQL queries using the cmbAreaCode parameter and apply input validation. Restrict database permissions to least privilege and conduct thorough security testing post-remediation.

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
Supplier 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Supplier Management System is installed
    Search the web root directory for files containing 'supplier management' or check installed web applications. Look for directories containing '/admin/' paths typical of this application.
    Affected if The application is present on the server
  2. Verify the application version is 1.0
    Check for version indicators such as: README files, version in footer, meta tags, or changelog files in the web root. Also check /admin/ for login pages that may display version info.
    Affected if The installed version is exactly 1.0
  3. Confirm the vulnerable file exists
    Check if the file /admin/add_retailer.php exists in the web root. This is the file containing the vulnerable cmbAreaCode parameter.
    Affected if The file /admin/add_retailer.php is present and accessible via web
  4. Test parameter accessibility
    Attempt to access the add_retailer.php page through the web interface. If the page requires authentication, note that unauthenticated access may still be possible depending on auth configuration.
    Affected if The page is accessible without proper access controls or the cmbAreaCode parameter can be manipulated
  5. Check for SQL injection indicators in application logs
    Review web server access logs and application logs for unusual SQL syntax in requests to /admin/add_retillerer.php. Look for patterns like single quotes, UNION statements, or SQL keywords in the cmbAreaCode parameter.
    Affected if Suspicious SQL patterns appear in logs for this endpoint
  6. Inspect the source code for the vulnerable parameter
    If source code is available, examine /admin/add_retillerer.php for direct use of $_POST or $_GET['cmbAreaCode'] in SQL queries without sanitization or prepared statements.
    Affected if The cmbAreaCode parameter is used in SQL queries without prepared statements or input escaping

A user is affected if they have Campcodes Supplier Management System version 1.0 running with the /admin/add_retailer.php file accessible and the cmbAreaCode parameter 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

Implement parameterized queries (prepared statements) for all SQL queries using the cmbAreaCode parameter and apply input validation. Restrict database permissions to least privilege and conduct thorough security testing post-remediation.

Fix this in Supplier Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14877 — 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-14877 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