# CVE-2018-25436: WordPress Plugin Baggage Freight Shipping Australia 0.1.0 Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files via the upload-package.php endpoint to achieve remote code execution.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-2v73-958c-qpgj

## What is CVE-2018-25436?

CVE-2018-25436 is a critical vulnerability in Shipster Baggage Freight Shipping Australia, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress Plugin Baggage Freight Shipping Australia 0.1.0 contains an unrestricted file upload vulnerability that allows unauthenticated attackers to upload arbitrary files by exploiting the upload-package.php endpoint. Attackers can submit POST requests with malicious file extensions to the upload handler, which moves files without validation to the plugin upload directory, enabling remote code execution.

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

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


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

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

## Is CVE-2018-25436 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25436 is a critical vulnerability in Shipster Baggage Freight Shipping Australia, published on 15 Jun 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-25436 exists.

Affected product: Shipster Baggage Freight Shipping Australia. 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-25436/ (Markdown: https://insights.sbomify.com/CVE-2018-25436/index.md)
```

## Sources

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

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