# CVE-2024-58275: Easywall 0.3.1 - Authenticated Command Injection in /ports-save Endpoint

> Authenticated attackers can execute arbitrary commands on the server via parameter injection in the /ports-save endpoint of Easywall.

- **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:** 4 Dec 2025
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-vgx4-pwq6-64p2

## What is CVE-2024-58275?

CVE-2024-58275 is a high-severity command injection vulnerability in jpylypiw Easywall, published on 4 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Easywall 0.3.1 allows authenticated remote command execution via a command injection vulnerability in the /ports-save endpoint that suffers from a parameter injection flaw. Attackers can inject shell metacharacters to execute arbitrary commands on the server.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2024-58275?


## How do I fix CVE-2024-58275?

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

## Is CVE-2024-58275 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58275 and fix it if it is affected.

What it is: CVE-2024-58275 is a high-severity command injection vulnerability in jpylypiw Easywall, published on 4 Dec 2025. 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-2024-58275 exists.

Affected product: jpylypiw Easywall. 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-2024-58275/ (Markdown: https://insights.sbomify.com/CVE-2024-58275/index.md)
```

## Sources

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

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