dbcve.org
Payroll Management SystemApplication · Campcodes

CVE-2025-7130

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-07
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 found in Campcodes Payroll Management System 1.0. It has been classified as critical. Affected is an unknown function of the file /ajax.php?action=delete_payroll. The manipulation of the argument ID leads to sql injection. It is possible to launch the attack 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 Payroll Management System 1.0 at the /ajax.php?action=delete_payroll endpoint allows remote attackers to manipulate the ID parameter to inject arbitrary SQL commands. The critical CVSS 9.8 score indicates potential for complete system compromise including data exfiltration or destruction.

MitigationImplement prepared statements/parameterized queries for all database operations, particularly the ID parameter in delete_payroll. Apply input validation and output encoding as defense-in-depth. Consider deploying a WAF as an interim control.

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. Confirm Campcodes Payroll Management System is installed
    Search the web root directory for files containing 'Campcodes' or 'Payroll Management System'. Check common paths like /var/www/html, /htdocs, or the web server document root for the application's source files.
    Affected if The application directory contains Campcodes Payroll Management System files
  2. Verify the application version is 1.0
    Check for a version file, README, or any file containing 'version' or '1.0' in the application root. Also check the footer or about page of the web interface if accessible.
    Affected if The installed version is exactly 1.0
  3. Confirm the vulnerable ajax.php endpoint exists
    Locate the ajax.php file in the web application directory and verify it contains a 'delete_payroll' case or handler for the action parameter.
    Affected if The file ajax.php with delete_payroll handler exists in the application
  4. Check if the application database is accessible
    Examine the application configuration files (often in includes, config, or db directories) for database connection strings. Verify the database server is reachable.
    Affected if The application has an active database connection
  5. Review the ID parameter handling in delete_payroll
    Open ajax.php and locate the code handling the 'delete_payroll' action. Inspect how the 'id' parameter is used in SQL queries - look for direct concatenation without parameterized queries or escaping functions.
    Affected if The ID parameter is used directly in SQL queries without prepared statements or proper escaping

A user is affected if Campcodes Payroll Management System version 1.0 is installed and the ajax.php file contains a delete_payroll handler where the ID parameter is not properly sanitized before use in 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

Implement prepared statements/parameterized queries for all database operations, particularly the ID parameter in delete_payroll. Apply input validation and output encoding as defense-in-depth. Consider deploying a WAF as an interim control.

Fix this in Payroll Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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