dbcve.org
Online Recruitment Management SystemApplication · Campcodes

CVE-2025-7135

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, which was classified as critical, has been found in Campcodes Online Recruitment Management System 1.0. This issue affects some unknown processing of the file /admin/ajax.php?action=save_vacancy. The manipulation of the argument 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 · moderate confidence

SQL injection vulnerability in Campcodes Online Recruitment Management System 1.0 allows remote attackers to execute arbitrary SQL queries via the ID parameter in the /admin/ajax.php?action=save_vacancy endpoint.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the ID parameter and all user-supplied input in the save_vacancy action; implement input validation and restrict database privileges.

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 Campcodes Online Recruitment Management System is installed
    Look for the application in your web server's document root. Common paths include /var/www/html/, /htdocs/, or C:\inetpub\wwwroot\. Identify the presence of files matching the application's structure (index.php, admin folder, etc.).
    Affected if The application directory exists on the server and is accessible via HTTP/HTTPS.
  2. Verify the vulnerable ajax.php endpoint exists
    Check for the presence of the file /admin/ajax.php within the application directory. If the file exists, confirm it contains the 'save_vacancy' action handler.
    Affected if The file /admin/ajax.php exists and contains code handling the 'save_vacancy' action.
  3. Check if the admin interface is accessible
    Attempt to access the /admin/ login page or ajax.php endpoint from a network perspective. Review web server access logs for requests to /admin/ajax.php?action=save_vacancy.
    Affected if The /admin/ajax.php endpoint is reachable from the network without authentication or with compromised admin credentials.
  4. Identify the ID parameter handling in save_vacancy
    Examine the source code of /admin/ajax.php to locate the save_vacancy action handler. Search for SQL queries that incorporate the ID parameter without proper sanitization or parameterized queries.
    Affected if The save_vacancy action directly uses the ID parameter in a SQL query without prepared statements or input validation.
  5. Check web server access logs for exploitation attempts
    Review web server access logs (Apache access.log, Nginx access.log) for requests to /admin/ajax.php?action=save_vacancy with suspicious ID values containing SQL syntax (e.g., quotes, UNION, SELECT, OR 1=1).
    Affected if Log entries show SQL injection patterns in the ID parameter for this endpoint.

You are affected if Campcodes Online Recruitment Management System 1.0 is running and the /admin/ajax.php?action=save_vacancy endpoint is accessible with the ID parameter being used directly 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

Replace dynamic SQL queries with parameterized queries/prepared statements for the ID parameter and all user-supplied input in the save_vacancy action; implement input validation and restrict database privileges.

Fix this in Online Recruitment Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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