# CVE-2020-11699: Command injection in n/a

> Authenticated attackers can execute remote code on SpamTitan servers via improper validation of the fname parameter in certs-x.php.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fwp6-grrh-7hj9

## What is CVE-2020-11699?

CVE-2020-11699 is a high-severity command injection vulnerability in n/a, published on 17 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Titan SpamTitan 7.07. Improper validation of the parameter fname on the page certs-x.php would allow an attacker to execute remote code on the target server. The user has to be authenticated before interacting with this page.

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

## Which versions are affected by CVE-2020-11699?

It affects 1 product.


Products: Titanhq Spamtitan.

## How do I fix CVE-2020-11699?

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

## Is CVE-2020-11699 being exploited?

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

Public exploit code:

- SpamTitan 7.07 - Remote Code Execution (Authenticated) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-11698](https://insights.sbomify.com/CVE-2020-11698/): Command injection in n/a (critical 9.8)
- [CVE-2020-11803](https://insights.sbomify.com/CVE-2020-11803/): Code injection in n/a (high 8.8)
- [CVE-2020-11804](https://insights.sbomify.com/CVE-2020-11804/): Code injection in n/a (high 8.8)
- [CVE-2019-6800](https://insights.sbomify.com/CVE-2019-6800/): Command injection in n/a (high 7.5)
- [CVE-2020-24045](https://insights.sbomify.com/CVE-2020-24045/): Security feature bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11699 and fix it if it is affected.

What it is: CVE-2020-11699 is a high-severity command injection vulnerability in n/a, published on 17 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11699 in the wild and no public exploit code.

Affected product: n/a. 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-2020-11699/ (Markdown: https://insights.sbomify.com/CVE-2020-11699/index.md)
```

## Sources

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

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