Quick answers
- Is CVE-2018-25390 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2018-25390 being exploited in the wild.
- How severe is CVE-2018-25390?
- High severity, with a CVSS score of 8.2, published 29 May 2026.
- Which products and versions are affected?
- HaPe PKH Project 1.1 and earlier.
- Is there a fix for CVE-2018-25390?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2018-25390 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2018-25390?
- Check whether you run HaPe PKH Project at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An SQL injection vulnerability exists in HaPe PKH version 1.1 and earlier due to improper neutralization of special elements in the 'desa' POST parameter within the 'lap-peserta-perdesa-pdf.php' component. An unauthenticated remote attacker can exploit this by sending a specially crafted HTTP POST request containing time-based blind SQL payloads. Successful exploitation allows the attacker to infer and extract sensitive information from the database. Additional vulnerable parameters and endpoints, such as 'nama_kelompok' and various 'id' parameters in the admin interface, have also been identified in public exploit reports.
Affected products
- HaPe PKH Project HaPe PKH 1.1 and earlier
Timeline
- 2018-10-12: disclosed: Initial exploit published on Exploit-DB
- 2026-05-29: advisory: NVD/VulnCheck advisory published