dbcve.org
Payroll Management SystemApplication · Campcodes

CVE-2025-7132

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 rated as critical. Affected by this issue is some unknown functionality of the file /ajax.php?action=save_payroll. The manipulation of the argument ID leads to sql injection. The attack may 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 Payroll Management System 1.0 affecting the /ajax.php?action=save_payroll endpoint. The 'ID' parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. With CVSS 9.8, the vulnerability is trivially exploitable remotely without authentication and can lead to complete compromise of confidentiality, integrity, and availability.

MitigationImmediately restrict network access to the affected endpoint until a patch is available; implement parameterized queries/prepared statements for all database operations and add input validation on the ID parameter. Consider disabling the payroll save functionality if immediate remediation is not possible.

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 the application is Campcodes Payroll Management System
    Locate the application installation directory and check for files or metadata indicating the product name and version. Look for a login page, header, or README file displaying the product name.
    Affected if The installed product is not Campcodes Payroll Management System version 1.0.
  2. Check if ajax.php exists in the web root
    Navigate to the web server document root and verify the presence of the ajax.php file. The vulnerability exists in this file at the save_payroll action endpoint.
    Affected if The ajax.php file does not exist or is not accessible via the web server.
  3. Verify the save_payroll action handler exists
    Open ajax.php and search for the string 'save_payroll' within the code to confirm the action handler is present.
    Affected if The 'save_payroll' action handler is not found in ajax.php.
  4. Inspect how the ID parameter is handled in save_payroll
    Locate the save_payroll code block in ajax.php and examine how the ID parameter is incorporated into database queries. Look for direct string concatenation or unsanitized variable insertion into SQL statements.
    Affected if The ID parameter is used directly in SQL queries without parameterized queries, prepared statements, or input sanitization functions.
  5. Check if the endpoint is accessible over the network
    Attempt to access http://[target]/ajax.php?action=save_payroll via a local HTTP request or verify the endpoint responds to requests. The vulnerability is exploitable remotely if the endpoint accepts requests.
    Affected if The ajax.php endpoint is exposed and accepts requests with the save_payroll action parameter.

A user is affected if they are running Campcodes Payroll Management System version 1.0 with the ajax.php file present and the ID parameter in the save_payroll action being used in unsanitized 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

Immediately restrict network access to the affected endpoint until a patch is available; implement parameterized queries/prepared statements for all database operations and add input validation on the ID parameter. Consider disabling the payroll save functionality if immediate remediation is not possible.

Fix this in Payroll Management System Scoped from the published advisory
  • Consultation8.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA4.0 h
42.0 hours of engineering $7,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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