CVE-2019-25499
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 · uneditedSimple Job Script contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the job_id parameter. Attackers can send POST requests to get_job_applications_ajax.php with malicious job_id values to bypass authentication, extract sensitive data, or modify database contents.
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 confidenceSimple Job Script contains an unauthenticated SQL injection vulnerability in get_job_applications_ajax.php. Attackers can inject malicious SQL code through the job_id parameter in POST requests to bypass authentication, extract sensitive data, or modify database contents.
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<= 1.66CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Simple Job Script installationLook for Simple Job Script PHP files on the web server, typically in the web root directory. Check for files like index.php, admin/, or a folder named 'simplejobscript' or 'sjs'.Affected if The application is not Simple Job Script or it is a different product entirely.
-
Identify installed versionCheck the version number in the source code. Common locations include a VERSION file, a config file, or the footer/admin panel. Search for version strings like 'v1.66' or 'version 1.66' in PHP files.Affected if The installed version is 1.66 or lower.
-
Locate vulnerable fileCheck if the file get_job_applications_ajax.php exists in the web-accessible directory, typically in the root or an includes/ajax/ folder.Affected if The file get_job_applications_ajax.php exists on the server.
-
Verify vulnerable code patternOpen get_job_applications_ajax.php and search for direct usage of $_POST['job_id'] in SQL queries without prepared statements or parameterization. Look for patterns like mysql_query, mysqli_query, or PDO query with the job_id variable inserted directly into the SQL string.Affected if The file contains direct insertion of the job_id POST parameter into SQL queries without prepared statements.
If the Simple Job Script version is 1.66 or lower AND the file get_job_applications_ajax.php exists with the job_id parameter used unsafely in SQL queries, the environment is affected by CVE-2019-25499.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with prepared statements/parameterized queries in get_job_applications_ajax.php and implement proper input validation on the job_id parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25499 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-25499 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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