# CVE-2018-25409: SIM-PKH 2.4.1 Arbitrary File Upload via aksi_pengurus.php

> Authenticated attackers can upload malicious PHP files to execute arbitrary code on the SIM-PKH web application.

- **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:** 30 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-j699-2v84-mrr9

## What is CVE-2018-25409?

CVE-2018-25409 is a high-severity vulnerability in Simpkh SIM-PKH, published on 30 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SIM-PKH 2.4.1 contains an arbitrary file upload vulnerability that allows authenticated attackers to upload malicious files by submitting PHP code through the fupload parameter. Attackers can upload PHP files via the aksi_pengurus.php endpoint with module=pengurus and act=update parameters, which are stored in the foto directory and executed as web scripts.

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

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


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

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

## Is CVE-2018-25409 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25409 is a high-severity vulnerability in Simpkh SIM-PKH, published on 30 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-25409 exists.

Affected product: Simpkh SIM-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-25409/ (Markdown: https://insights.sbomify.com/CVE-2018-25409/index.md)
```

## Sources

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

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