dbcve.org
Online Job Finder SystemApplication · Campcodes

CVE-2025-10444

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
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 security flaw has been discovered in Campcodes Online Job Finder System 1.0. This issue affects some unknown processing of the file /advancesearch.php. Performing manipulation of the argument Username results in sql injection. The attack is possible to be carried out remotely. The exploit has been released to the public and may be exploited.

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 Job Finder System 1.0 allows remote attackers to execute arbitrary SQL commands via the Username parameter in /advancesearch.php. The lack of input sanitization or parameterized queries enables unauthenticated attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries for the Username parameter in advancesearch.php, or apply vendor security patch if available. Consider implementing input validation and WAF rules as additional layers of defense.

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 Job Finder 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
    Locate Campcodes Online Job Finder System files on the server. Common paths may include web root directories such as /var/www/html/, /www/, or C:\inetpub\wwwroot\ depending on the operating system. Look for directories containing job portal or recruitment-related PHP files.
    Affected if The Campcodes Online Job Finder System application is present on the server.
  2. Verify the application version
    Check for version identification files or headers within the application installation directory. Common locations include a README file, version.php, or the main index.php which may contain version metadata.
    Affected if The installed version is 1.0.
  3. Locate the vulnerable script
    Search for the file advancesearch.php within the web application directory structure. This file should exist in the main application folder accessible via web requests.
    Affected if The file advancesearch.php exists in the application.
  4. Inspect the Username parameter handling
    Open advancesearch.php in a text editor and locate the code that processes the Username parameter from user input. Examine how this parameter is used in database queries - specifically look for direct concatenation of the Username value into SQL statements without using prepared statements, binding parameters, or input sanitization functions.
    Affected if The Username parameter from user input is included directly in SQL queries without parameterized queries, prepared statements, or proper sanitization.

The environment is affected if Campcodes Online Job Finder System version 1.0 is installed with the advancesearch.php file present and the Username parameter is used in SQL queries without prepared statements or 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.

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

Replace dynamic SQL queries with prepared statements/parameterized queries for the Username parameter in advancesearch.php, or apply vendor security patch if available. Consider implementing input validation and WAF rules as additional layers of defense.

Recommended fix Low confidence
  1. 1. Locate the file /advancesearch.php in the web application root directory
  2. 2. Identify the code handling the 'Username' parameter (typically via $_POST or $_GET)
  3. 3. Replace all direct string concatenation or interpolation of user input into SQL queries with prepared statements/parameterized queries
  4. 4. For PHP with MySQL, use PDO or mysqli with placeholders: $stmt = $pdo->prepare('SELECT * FROM table WHERE Username = :username'); $stmt->execute([':username' => $username]);
  5. 5. Ensure all database interactions using the Username parameter are protected against SQL injection
  6. 6. Test the advancesearch.php functionality to confirm the fix does not break existing features
  7. 7. Deploy the fixed file to production

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

Fix this in Online Job Finder System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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