# CVE-2018-25386: HaPe PKH 1.1 SQL Injection via id Parameter in admin/media.php

> Unauthenticated attackers can inject SQL via the id parameter in admin/media.php to extract sensitive database information from HaPe PKH.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-86v9-rw4q-v83j

## What is CVE-2018-25386?

CVE-2018-25386 is a high-severity SQL injection vulnerability in Sitejo HaPe PKH, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HaPe PKH 1.1 contains multiple SQL injection vulnerabilities in admin/media.php that allow attackers to manipulate database queries by injecting SQL code through the 'id' parameter. An unauthenticated attacker can exploit the desa module (module=desa&act=hapus), while authenticated users can exploit the pengurus, fasilitas, and kelompok modules (for example act=print, act=editpengurus, act=editfasilitas, and act=editkelompok). Successful exploitation allows extraction of sensitive database information including the current user, database name, and DBMS version.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2018-25386?


## How do I fix CVE-2018-25386?

No fix has been published for CVE-2018-25386 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-25386 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25386 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25386 and fix it if it is affected.

What it is: CVE-2018-25386 is a high-severity SQL injection vulnerability in Sitejo HaPe PKH, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25386 exists.

Affected product: Sitejo HaPe PKH. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-25386/ (Markdown: https://insights.sbomify.com/CVE-2018-25386/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-25386
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-25386
- OSV: https://osv.dev/vulnerability/CVE-2018-25386

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-25386/
Summaries are generated and may contain mistakes; the official description above is the record.