dbcve.org
Supplier Management SystemApplication · Campcodes

CVE-2025-13554

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-23
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 security vulnerability has been detected in Campcodes Supplier Management System 1.0. This impacts an unknown function of the file /index.php of the component Login. Such manipulation of the argument txtUsername leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed publicly 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 the Login component of Campcodes Supplier Management System 1.0 at /index.php. The txtUsername parameter is not properly sanitized, allowing unauthenticated remote attackers to inject arbitrary SQL queries via the login form, potentially enabling authentication bypass and complete database compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the login function. Apply input validation and escaping for all user inputs. Apply vendor patch when available.

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
    Locate the web application root directory and verify the presence of /index.php and other supplier management system files. Check for files like 'supplier', 'supplier.php', or login-related components.
    Affected if The application is Campcodes Supplier Management System and /index.php exists in the web root
  2. Verify the installed version is 1.0
    Check the application for a version identifier. Look in source files, README, or configuration files for version = 1.0. Common locations include a 'version' file, footer in UI, or in the main index.php file.
    Affected if Installed version is exactly 1.0
  3. Confirm the login page is accessible
    Access the login page at /index.php via HTTP/HTTPS request. Verify the page loads and contains a login form with a username field.
    Affected if The login form at /index.php is accessible and responds to requests
  4. Check for txtUsername parameter in login form
    Inspect the HTML source of the login form at /index.php. Look for an input field with name='txtUsername' that accepts user credentials.
    Affected if A login form field named 'txtUsername' exists in the page
  5. Verify dynamic SQL usage in login code
    Examine the server-side code at /index.php or included login handling files. Search for SQL queries that incorporate the txtUsername parameter directly without parameterized queries or escaping.
    Affected if The login code builds SQL queries using the txtUsername parameter without prepared statements or input sanitization

If the Campcodes Supplier Management System version 1.0 is running with the login form at /index.php accessible and the txtUsername parameter is used in unsanitized SQL queries, the environment is affected by CVE-2025-13554.

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 for the login function. Apply input validation and escaping for all user inputs. Apply vendor patch when available.

Fix this in Supplier Management System Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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