dbcve.org
Online Recruitment Management SystemApplication · Campcodes

CVE-2025-5677

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-05
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 Online Recruitment Management System 1.0. It has been rated as critical. This issue affects some unknown processing of the file /admin/ajax.php?action=save_application. The manipulation of the argument position_id leads to sql injection. The attack may 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 · high confidence

SQL injection vulnerability in Campcodes Online Recruitment Management System 1.0 allows remote attackers to inject malicious SQL queries via the position_id parameter in the /admin/ajax.php?action=save_application endpoint. The lack of parameterized queries or proper input sanitization enables attackers to manipulate database queries.

MitigationImplement prepared statements/parameterized queries for all database operations, particularly for the position_id parameter in the save_application action. Apply input validation and sanitize all user-supplied values before using them in SQL 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. Identify application and version
    Inspect the application source files, typically found in the web root directory. Look for version indicators in files like readme.txt, version.php, or the main index.php. Alternatively, check HTTP response headers or the admin login page source for version information.
    Affected if The application is Campcodes Online Recruitment Management System version 1.0 exactly.
  2. Locate the vulnerable ajax.php file
    Check if the file /admin/ajax.php exists in the web root directory. This file handles the save_application action and contains the vulnerable position_id parameter processing.
    Affected if The file /admin/ajax.php exists and contains the save_application action handler.
  3. Verify admin panel access
    Confirm the /admin/ directory is accessible. Try accessing the admin login page or ajax endpoint directly via HTTP request. The vulnerability requires access to the admin functionality.
    Affected if The /admin/ajax.php endpoint is reachable without additional authentication barriers beyond normal admin access.
  4. Inspect the position_id parameter handling
    Review the source code of /admin/ajax.php and look for the save_application case. Search for database query execution involving $_POST['position_id'] or $_GET['position_id'] without prepared statements or input sanitization.
    Affected if The code directly uses the position_id parameter in SQL queries without parameterized queries, proper escaping, or input validation.

You are affected if you are running Campcodes Online Recruitment Management System version 1.0 and the /admin/ajax.php file with the save_application action processes the position_id parameter using unsafe 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations, particularly for the position_id parameter in the save_application action. Apply input validation and sanitize all user-supplied values before using them in SQL queries.

Recommended fix Moderate confidence
  1. Restrict network access to /admin/ajax.php?action=save_application to trusted admin IP addresses only (e.g., using .htaccess, nginx allow/deny, or a firewall rule).
  2. Deploy a Web Application Firewall (WAF) rule that detects and blocks SQL injection patterns in the position_id parameter.
  3. If the save_application functionality is not needed in production, disable it by removing the action handler or renaming the file.
  4. As a permanent fix, modify the code in /admin/ajax.php to use prepared statements (PDO or MySQLi) when handling the position_id argument, binding the parameter instead of concatenating user input.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Online Recruitment Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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