# CVE-2021-4466: IPCop <= 2.1.9 Authenticated RCE

> Authenticated attackers can execute arbitrary OS commands via the email configuration interface, leading to full system compromise.

- **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:** 14 Nov 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-vggq-52m7-59x7

## What is CVE-2021-4466?

CVE-2021-4466 is a high-severity command injection vulnerability in IPCop, published on 14 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IPCop versions up to and including 2.1.9 contain an authenticated remote code execution vulnerability within the web-based administration interface. The email configuration component inserts user-controlled values, including the EMAIL_PW parameter, directly into system-level operations without proper input sanitation. By modifying the email password field to include shell metacharacters and issuing a save-and-test-mail action, an authenticated attacker can execute arbitrary operating system commands with the privileges of the web interface, resulting in full system compromise.

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

## Which versions are affected by CVE-2021-4466?


## How do I fix CVE-2021-4466?

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

## Is CVE-2021-4466 being exploited?

There is no known exploitation of CVE-2021-4466 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-4466 and fix it if it is affected.

What it is: CVE-2021-4466 is a high-severity command injection vulnerability in IPCop, published on 14 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-4466 in the wild and no public exploit code.

Affected product: IPCop. 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-2021-4466/ (Markdown: https://insights.sbomify.com/CVE-2021-4466/index.md)
```

## Sources

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

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