# CVE-2018-25391: HaPe PKH 1.1 Missing Authorization Allows Unauthenticated Record Deletion

> Unauthenticated attackers can delete arbitrary administrator and update records in HaPe PKH due to missing authorization checks on deletion endpoints.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/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-jv33-m8x5-6599

## What is CVE-2018-25391?

CVE-2018-25391 is a high-severity missing authorization 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 fails to enforce authorization on its record deletion endpoints, allowing unauthenticated attackers to delete arbitrary records by sending a crafted request that specifies the target record's id. The admin/modul/mod_pengurus/aksi_pengurus.php (module=pengurus&act=hapus) and admin/modul/mod_update/aksi_update.php (module=update&act=hapus) endpoints process deletions without verifying the requester's privileges, enabling removal of pengurus (administrator) and update records.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2018-25391 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25391 is a high-severity missing authorization 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-25391 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-25391/ (Markdown: https://insights.sbomify.com/CVE-2018-25391/index.md)
```

## Sources

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

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