# CVE-2018-25388: HaPe PKH 1.1 Arbitrary File Upload via aksi_foto.php

> Authenticated attackers can upload malicious PHP files to execute arbitrary code on the server by bypassing file type validation.

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

## What is CVE-2018-25388?

CVE-2018-25388 is a high-severity vulnerability in Sitejo HaPe PKH, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HaPe PKH 1.1 contains an arbitrary file upload vulnerability that allows authenticated attackers to upload malicious files by bypassing file type validation. Attackers can upload PHP files through multiple endpoints including aksi_foto.php, aksi_user.php, and aksi_kecamatan.php to execute arbitrary code on the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2018-25388 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25388 is a high-severity vulnerability in Sitejo HaPe PKH, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25388 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-25388/ (Markdown: https://insights.sbomify.com/CVE-2018-25388/index.md)
```

## Sources

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

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