# CVE-2025-5030: Ackites KillWxapkg wxapkg File Parser unpack.go processFile os command injection

> Remote attackers can execute arbitrary OS commands via crafted wxapkg files in the KillWxapkg Go library, requiring high complexity.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 May 2025
- **Updated:** 21 May 2025
- **Also known as:** GHSA-w6p4-84vc-qc2w, GO-2025-3773

## What is CVE-2025-5030?

CVE-2025-5030 is a low-severity command injection vulnerability in Ackites KillWxapkg, published on 21 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in Ackites KillWxapkg up to 2.4.1. It has been declared as critical. This vulnerability affects the function processFile of the file internal/unpack/unpack.go of the component wxapkg File Parser. The manipulation leads to os command injection. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-5030?

3 open source packages ship an affected version, including github.com/Ackites/KillWxapkg. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/Ackites/KillWxapkg` | Go | All versions | None |
| `github.com/Ackites/KillWxapkg` | Go | All versions to 1.1.0 | None |
| `github.com/Ackites/KillWxapkg` | Go | All versions to 1.1.0 | None |

Products: Ackites Killwxapkg.

## How do I fix CVE-2025-5030?

Upgrade to a fixed version.

## Is CVE-2025-5030 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5030 and fix it if it is affected.

What it is: CVE-2025-5030 is a low-severity command injection vulnerability in Ackites KillWxapkg, published on 21 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5030 exists.

Affected packages and fixed versions:
- github.com/Ackites/KillWxapkg (Go): affected all versions; no fix listed
- github.com/Ackites/KillWxapkg (Go): affected all versions up to 1.1.0; no fix listed
- github.com/Ackites/KillWxapkg (Go): affected all versions up to 1.1.0; no fix listed

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-2025-5030/ (Markdown: https://insights.sbomify.com/CVE-2025-5030/index.md)
```

## Sources

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

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