dbcve.org
Online Recruitment Management SystemApplication · Campcodes

CVE-2025-7136

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, was found in Campcodes Online Recruitment Management System 1.0. Affected is an unknown function of the file /admin/view_vacancy.php. 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 Online Recruitment Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /admin/view_vacancy.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or complete system compromise.

MitigationReplace dynamic SQL queries in view_vacancy.php with parameterized queries/prepared statements to properly sanitize the ID parameter. If no vendor patch is available, implement strict input validation and consider deploying a WAF as a temporary compensating control until the code can be properly remediated.

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 installed
    Identify if Campcodes Online Recruitment Management System is running in your environment by checking web server directories, application inventories, or by accessing the application's login or landing page and reviewing any version information displayed.
    Affected if The application Campcodes Online Recruitment Management System is present in the environment
  2. Verify the installed version
    Check the version number of the installed Campcodes Online Recruitment Management System. Look for version indicators in the application source code, admin panel, or any version documentation files included with the deployment.
    Affected if The installed version is exactly 1.0
  3. Locate the vulnerable PHP file
    Check if the file /admin/view_vacancy.php exists in the web application's directory structure. This file is typically found in the admin section of the application.
    Affected if The file /admin/view_vacancy.php exists in the deployed application
  4. Verify admin panel accessibility
    Determine if the /admin/ directory and specifically view_vacancy.php are accessible over the network. Check web server configuration for any access restrictions (IP allowlists, authentication requirements) that may limit exposure to the vulnerable endpoint.
    Affected if The /admin/view_vacancy.php endpoint is accessible without additional authentication or from an untrusted network source
  5. Inspect the ID parameter handling
    Review the source code of view_vacancy.php to verify whether the ID parameter is processed using prepared statements/parameterized queries or raw SQL concatenation. Search for SQL query patterns that directly incorporate the ID parameter without sanitization.
    Affected if The ID parameter in view_vacancy.php is used directly in SQL queries without prepared statements or input sanitization

You are affected if you are running Campcodes Online Recruitment Management System version 1.0 with the /admin/view_vacancy.php file accessible and the ID parameter handled without parameterized 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 in view_vacancy.php with parameterized queries/prepared statements to properly sanitize the ID parameter. If no vendor patch is available, implement strict input validation and consider deploying a WAF as a temporary compensating control until the code can be properly remediated.

Fix this in Online Recruitment Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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