dbcve.org
Supplier Management SystemApplication · Campcodes

CVE-2025-14515

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-11
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 has been found in Campcodes Supplier Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/add_unit.php. Such manipulation of the argument txtunitDetails leads to sql injection. The attack can 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 Supplier Management System 1.0 allows remote attackers to inject malicious SQL code via the txtunitDetails parameter in /admin/add_unit.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries and implement proper input validation on the txtunitDetails parameter. Apply 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
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. Identify if Campcodes Supplier Management System is installed
    Search for files or directories containing 'supplier' or check web root for Campcodes installation folders. Look for the presence of /admin/add_unit.php in the web directory.
    Affected if The application is present on the server and the affected file /admin/add_unit.php exists
  2. Confirm the installed version is 1.0
    Check version information in the application (typically in README, version file, or admin dashboard). Compare against the affected version range: 1.0
    Affected if The installed version is exactly 1.0
  3. Locate the vulnerable add_unit.php script
    Navigate to the web directory and locate the file /admin/add_unit.php. Open it and search for usage of the txtunitDetails parameter without prepared statements or input sanitization.
    Affected if The file exists and the txtunitDetails parameter is processed without parameterized queries or input validation
  4. Check if the admin interface is accessible
    Attempt to access the /admin/ directory or /admin/add_unit.php via HTTP/HTTPS to determine if the vulnerable endpoint is exposed.
    Affected if The admin panel and the vulnerable script are accessible over the network
  5. Review database query handling in the affected file
    Examine the source code of add_unit.php for direct use of txtunitDetails in SQL queries (look for $sql = "..." constructions without prepare() or bindParam() calls).
    Affected if The txtunitDetails parameter is concatenated directly into SQL queries without sanitization or parameterized binding

A user is affected if Campcodes Supplier Management System version 1.0 is installed, the /admin/add_unit.php file exists and is accessible, and the txtunitDetails parameter is handled without prepared statements or input sanitization in the SQL queries.

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 prepared statements/parameterized queries and implement proper input validation on the txtunitDetails parameter. Apply principle of least privilege to the database user.

Fix this in Supplier Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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