dbcve.org
Online Recruitment Management SystemApplication · Campcodes

CVE-2025-8274

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-28
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 classified as critical was found in Campcodes Online Recruitment Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/ajax.php?action=save_recruitment_status. 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 · high confidence

A critical SQL injection vulnerability exists in Campcodes Online Recruitment Management System 1.0 within the /admin/ajax.php file's save_recruitment_status action. The ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries and potentially extract, modify, or delete database contents.

MitigationImplement prepared statements/parameterized queries for the ID parameter in the save_recruitment_status action. Additionally, apply input validation and proper escaping for all user-supplied parameters before database queries.

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
Online Recruitment 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 Online Recruitment Management System
    Locate the application files or check the web application's title/page footer for the product name. This system is typically deployed as a PHP web application.
    Affected if The installed application is not Campcodes Online Recruitment Management System version 1.0, then this CVE does not apply.
  2. Identify the affected PHP file
    Locate the file /admin/ajax.php in the web application directory structure. This file handles AJAX requests including the save_recruitment_status action.
    Affected if The file /admin/ajax.php does not exist in the deployment, the vulnerability is not present.
  3. Check if the save_recruitment_status action exists
    Examine the /admin/ajax.php file for a function or handler named 'save_recruitment_status' or similar. This action processes recruitment status updates.
    Affected if The save_recruitment_status action is not implemented in ajax.php, the vulnerability is not present.
  4. Verify the ID parameter is processed without sanitization
    Review the source code of the save_recruitment_status handler in /admin/ajax.php. Look for how the ID parameter is obtained (e.g., $_POST, $_GET) and whether it is used directly in SQL queries without prepared statements, parameter binding, or escaping functions.
    Affected if The ID parameter is used in SQL queries without proper sanitization (no prepared statements, no escaping, no input validation), the system is vulnerable to SQL injection.
  5. Confirm admin panel accessibility
    Determine if the /admin/ajax.php endpoint is accessible to remote users. Check if authentication is required or if the save_recruitment_status action can be invoked without authentication.
    Affected if The save_recruitment_status action is accessible without authentication and the ID parameter is not sanitized, the vulnerability is exploitable remotely.

A user is affected if they are running Campcodes Online Recruitment Management System version 1.0 with the /admin/ajax.php file containing a save_recruitment_status action that uses the ID parameter in SQL queries without prepared statements or input sanitization.

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 the ID parameter in the save_recruitment_status action. Additionally, apply input validation and proper escaping for all user-supplied parameters before database queries.

Fix this in Online Recruitment Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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