dbcve.org
Employee Management SystemApplication · Campcodes

CVE-2025-6954

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-01
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 Employee Management System 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /applyleave.php. The manipulation of the argument ID 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 · moderate confidence

A SQL injection vulnerability exists in the ID parameter of /applyleave.php in Campcodes Employee Management System 1.0, allowing remote attackers to inject arbitrary SQL commands due to unsanitized user input being directly used in database queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the ID parameter, audit the entire application for similar SQL injection vulnerabilities, and apply vendor patches if 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
Employee 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 the installed application
    Locate Campcodes Employee Management System in your environment. Check for the presence of the web application files, typically in the web server root directory (e.g., /var/www/html/, /htdocs/, or C:\inetpub\wwwroot\). Look for application files or check web server configuration for this application.
    Affected if Campcodes Employee Management System is present in the environment.
  2. Confirm the version number
    Check the application's version. This may be displayed in the login page, an about page, a README file, or meta tags within the HTML. Compare the installed version to the affected range: version 1.0.
    Affected if The installed version is exactly 1.0.
  3. Verify the vulnerable file exists
    Locate the file applyleave.php within the web application directory. Common paths include /applyleave.php or /modules/leave/applyleave.php. Use file system search or check the source code structure.
    Affected if The file applyleave.php exists in the web application.
  4. Check if the application is network-accessible
    Determine if the web application is accessible over the network (HTTP/HTTPS). Attempt to access the vulnerable endpoint by navigating to the full URL (e.g., http://[host]/applyleave.php or the identified path).
    Affected if The application is accessible over the network and the applyleave.php endpoint responds.
  5. Verify the ID parameter is processed
    Test if the ID parameter is accepted by the application. Submit a request to applyleave.php with an ID parameter (e.g., ?id=1). Check if the application processes this parameter and includes it in database queries without sanitization.
    Affected if The ID parameter is accepted and processed by applyleave.php without input validation.

If Campcodes Employee Management System version 1.0 is installed, the file applyleave.php exists, the application is network-accessible, and the ID parameter is processed, the environment is affected by this SQL injection vulnerability.

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 ID parameter, audit the entire application for similar SQL injection vulnerabilities, and apply vendor patches if available.

Fix this in Employee Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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