CVE-2016-15018 json
krail-jpa sql injection
published 2023-01-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2016-2088
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
A vulnerability was found in krail-jpa up to 0.9.1. It has been classified as critical. This affects an unknown part. The manipulation leads to sql injection. Upgrading to version 0.9.2 is able to address this issue. The identifier of the patch is c1e848665492e21ef6cc9be443205e36b9a1f6be. It is recommended to upgrade the affected component. The identifier VDB-218373 was assigned to this vulnerability.
Patch / fix
- krail-jpa_project krail-jpa 0.9.2
Exploit prediction
0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/KrailOrg/krail-jpa/issues/18 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.0 | 5.5 | CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 2.0 | 5.2 | AV:A/AC:L/Au:S/C:P/I:P/A:P |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- n/a krail-jpa
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/KrailOrg/krail-jpa/commit/c1e848665492e21ef6cc9be443205e36b9a1f6be
patch, third-party-advisory
-
github.com
/KrailOrg/krail-jpa/releases/tag/0.9.2
patch, release-notes, third-party-advisory
-
github.com
/KrailOrg/krail-jpa/issues/18
issue-tracking, exploit, patch, third-party-advisory
-
vuldb.com
/?id.218373
vdb-entry, technical-description, permissions-required, third-party-advisory
-
vuldb.com
/?ctiid.218373
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2016-15018
- NVD CVE-2016-15018
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.