dbcve.org
Payroll Management SystemApplication · Campcodes

CVE-2025-7217

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-09
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 Payroll Management System 1.0 and classified as critical. This vulnerability affects unknown code of the file /ajax.php?action=save_position. The manipulation of the argument ID leads to sql injection. The attack can be initiated 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

SQL injection vulnerability in Campcodes Payroll Management System 1.0 allows remote attackers to inject malicious SQL code via the ID parameter in the /ajax.php?action=save_position endpoint. The lack of input sanitization or parameterized queries enables arbitrary database manipulation.

MitigationImplement prepared statements/parameterized queries for all database operations, particularly for the ID parameter in the save_position action. Conduct a comprehensive code review to identify and remediate additional injection points.

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
Payroll 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. Locate Campcodes Payroll Management System installation
    Search the server for files named 'payroll', 'payroll management', or check common web root directories (/var/www/html, /opt, C:\inetpub\wwwroot) for Campcodes or payroll-related folders. Identify the application directory path.
    Affected if The application is found installed on the system.
  2. Confirm installed version is 1.0
    Check for version files (version.txt, about.php, or footer/header includes) within the application directory, or access the application's About/Info page if available. Compare the discovered version to the affected range.
    Affected if The installed version is exactly 1.0.
  3. Verify ajax.php exists in web-accessible path
    Locate the ajax.php file within the application web directory. This file typically resides in the root or admin folder of the Payroll Management System.
    Affected if ajax.php file is present in the application web directory.
  4. Check for save_position action handler
    Open ajax.php and search for the string 'save_position' or 'case "save_position"' to verify the vulnerable action handler exists in the code.
    Affected if The save_position action handler is defined in ajax.php.
  5. Determine if application is network-accessible
    Verify the application is accessible over HTTP/HTTPS from a client machine. Check network configuration, firewall rules, or try accessing the application's login page or ajax.php endpoint via a browser or curl command.
    Affected if The application web interface is exposed on the network.

You are affected if you are running Campcodes Payroll Management System version 1.0 with the ajax.php file containing the save_position action, and the application is network-accessible.

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 prepared statements/parameterized queries for all database operations, particularly for the ID parameter in the save_position action. Conduct a comprehensive code review to identify and remediate additional injection points.

Fix this in Payroll Management System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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