dbcve.org
SimplejobscriptApplication

CVE-2020-7229

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-21
Fix available
A fix is available. Upgrade to 1.65 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An issue was discovered in Simplejobscript.com SJS before 1.65. There is unauthenticated SQL injection via the search engine. The parameter is landing_location. The function is countSearchedJobs(). The file is _lib/class.Job.php.

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

Unauthenticated SQL injection in Simple Job Script (SJS) before version 1.65 allows remote attackers to inject malicious SQL queries via the 'landing_location' parameter in the search functionality. The vulnerability exists in the countSearchedJobs() function within _lib/class.Job.php.

MitigationUpgrade to SJS version 1.65 or later, and refactor countSearchedJobs() to use parameterized queries/prepared statements instead of string concatenation for the landing_location parameter.

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
SimplejobscriptApplication
Affected:< 1.65

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 Simple Job Script installation
    Locate the web application directory and confirm the presence of Simple Job Script (SJS) files, typically found in the web root. Look for characteristic SJS files such as index.php, config.php, or directories like _lib/ or templates/.
    Affected if Simple Job Script is not present on the server - not applicable.
  2. Determine installed SJS version
    Check for a version file, changelog, or config file within the SJS installation. Common locations include a version constant in index.php, a changelog.txt file, or the config.php file. Compare the found version against the affected range.
    Affected if The installed version is 1.64 or lower, or the version cannot be determined and falls within the < 1.65 range.
  3. Verify vulnerable file exists
    Locate the file _lib/class.Job.php within the SJS installation directory. Confirm the file exists and contains the countSearchedJobs() function.
    Affected if The file _lib/class.Job.php exists and contains the countSearchedJobs function.
  4. Check if search functionality is exposed
    Identify if the search functionality using the landing_location parameter is accessible on the site. This typically involves checking if the job search feature is publicly accessible without authentication.
    Affected if The search functionality with the landing_location parameter is publicly accessible without authentication.

The environment is affected if Simple Job Script is installed with a version below 1.65 and the search feature exposing the landing_location parameter is publicly accessible.

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
Upgrade available Upgrade to 1.65 or later
Fixed in 1.65
Interim mitigation

Upgrade to SJS version 1.65 or later, and refactor countSearchedJobs() to use parameterized queries/prepared statements instead of string concatenation for the landing_location parameter.

Recommended fix High confidence

Simplejobscript 1.65

  1. 1. Back up the entire Simplejobscript installation directory and database before making any changes.
  2. 2. Download Simplejobscript version 1.65 (or the latest stable release) from the official source at simplejobscript.com.
  3. 3. Replace the existing _lib/class.Job.php file with the updated version from the 1.65 release.
  4. 4. Clear any application caches if caching is enabled.
  5. 5. Test the search functionality to confirm the SQL injection vulnerability is remediated.
  6. 6. Verify that the landing_location parameter is now properly sanitized or parameterized in queries.
Caveat Review the changelog between your current version and 1.65 for any configuration or template changes that may require adjustments.

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

Fix this in Simplejobscript Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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