CVE-2019-25499

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Simple 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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

March 4, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

SJS Simple Job Script - SQL Injection / Cross-Site Scripting - PHP webapps Exploit

https://www.exploit-db.com/exploits/46612

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:22 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-16 14:04 UTCEPSS rescore
  4. 2026-09-15 03:05 UTCEPSS rescore
  5. 2026-09-13 16:42 UTCEPSS rescore
  6. 2026-09-12 14:56 UTCEPSS rescore
  7. 2026-09-11 14:48 UTCEPSS rescore
  8. 2026-09-11 09:32 UTCEPSS rescore
  9. 2026-09-07 15:57 UTCEPSS rescore
  10. 2026-09-06 13:44 UTCEPSS rescore
  11. 2026-09-05 15:24 UTCEPSS rescore
  12. 2026-09-04 13:56 UTCEPSS rescore
  13. 2026-09-02 14:07 UTCEPSS rescore
  14. 2026-09-01 03:32 UTCEPSS rescore
  15. 2026-08-30 19:13 UTCEPSS rescore
  16. 2026-08-30 01:18 UTCEPSS rescore
  17. 2026-08-28 21:36 UTCEPSS rescore
  18. 2026-08-27 14:21 UTCEPSS rescore
  19. 2026-08-26 14:42 UTCEPSS rescore
  20. 2026-08-25 13:45 UTCEPSS rescore
  21. 2026-08-24 14:11 UTCEPSS rescore
  22. 2026-08-21 23:45 UTCEPSS rescore
  23. 2026-08-20 22:51 UTCEPSS rescore
  24. 2026-08-19 17:00 UTCEPSS rescore
  25. 2026-08-18 13:44 UTCEPSS rescore
Show 57 more
  1. 2026-08-17 13:43 UTCEPSS rescore
  2. 2026-08-16 14:52 UTCEPSS rescore
  3. 2026-08-16 02:10 UTCEPSS rescore
  4. 2026-08-15 01:26 UTCEPSS rescore
  5. 2026-08-15 00:34 UTCGHSA enrichment
  6. 2026-08-14 20:57 UTCGHSA enrichment
  7. 2026-08-14 15:49 UTCGHSA enrichment
  8. 2026-08-14 12:12 UTCGHSA enrichment
  9. 2026-08-14 08:35 UTCEG score recompute
  10. 2026-08-14 08:35 UTCGHSA enrichment
  11. 2026-08-13 03:55 UTCGHSA enrichment
  12. 2026-08-13 00:18 UTCEG score recompute
  13. 2026-08-13 00:18 UTCGHSA enrichment
  14. 2026-08-12 13:47 UTCEPSS rescore
  15. 2026-08-11 23:15 UTCEG score recompute
  16. 2026-08-11 23:15 UTCGHSA enrichment
  17. 2026-08-11 05:48 UTCEG score recompute
  18. 2026-08-11 05:48 UTCGHSA enrichment
  19. 2026-08-10 13:03 UTCGHSA enrichment
  20. 2026-08-10 08:15 UTCGHSA enrichment
  21. 2026-08-10 04:37 UTCGHSA enrichment
  22. 2026-08-10 00:53 UTCGHSA enrichment
  23. 2026-08-09 21:15 UTCGHSA enrichment
  24. 2026-08-09 17:37 UTCEG score recompute
  25. 2026-08-09 17:37 UTCGHSA enrichment
  26. 2026-08-09 13:43 UTCEPSS rescore
  27. 2026-08-09 13:38 UTCGHSA enrichment
  28. 2026-08-09 08:13 UTCEG score recompute
  29. 2026-08-09 08:13 UTCGHSA enrichment
  30. 2026-08-08 16:33 UTCEPSS rescore
  31. 2026-08-08 11:33 UTCGHSA enrichment
  32. 2026-08-08 06:58 UTCGHSA enrichment
  33. 2026-08-08 03:20 UTCGHSA enrichment
  34. 2026-08-07 23:42 UTCGHSA enrichment
  35. 2026-08-07 20:05 UTCEG score recompute
  36. 2026-08-07 20:05 UTCGHSA enrichment
  37. 2026-08-07 16:23 UTCEPSS rescore
  38. 2026-08-06 13:43 UTCEPSS rescore
  39. 2026-08-06 06:18 UTCGHSA enrichment
  40. 2026-08-06 02:41 UTCEG score recompute
  41. 2026-08-06 02:41 UTCGHSA enrichment
  42. 2026-08-05 19:13 UTCEPSS rescore
  43. 2026-08-04 15:05 UTCEPSS rescore
  44. 2026-08-04 02:36 UTCEG score recompute
  45. 2026-08-04 02:36 UTCGHSA enrichment
  46. 2026-08-03 02:32 UTCGHSA enrichment
  47. 2026-08-02 22:36 UTCGHSA enrichment
  48. 2026-08-02 18:59 UTCEG score recompute
  49. 2026-08-02 18:59 UTCGHSA enrichment
  50. 2026-08-01 04:12 UTCEPSS rescore
  51. 2026-07-30 16:24 UTCEPSS rescore
  52. 2026-07-30 01:27 UTCEPSS rescore
  53. 2026-07-28 15:32 UTCEPSS rescore
  54. 2026-07-28 02:25 UTCEG score recompute
  55. 2026-07-28 02:25 UTCGHSA enrichment
  56. 2026-07-27 13:52 UTCEG score recompute
  57. 2026-07-27 13:52 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2019-25499?
CVE-2019-25499 is a critical vulnerability published on March 4, 2026. Simple Job Script contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the jobid parameter. Attackers can send POST requests to getjobapplicationsajax.php with malicious job_id values to bypass authentication,…
When was CVE-2019-25499 disclosed?
CVE-2019-25499 was first published in the National Vulnerability Database on March 4, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25499 actively exploited?
CVE-2019-25499 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.3% of all scored CVEs.
What is the CVSS score of CVE-2019-25499?
CVE-2019-25499 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-25499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25499, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-25499

Explore →

Is Your Infrastructure Affected by CVE-2019-25499?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs