# CVE-2016-7844: Command injection in GigaCC OFFICE

> Remote attackers can execute arbitrary OS commands via crafted mail templates in GigaCC OFFICE, requiring an upgrade to mitigate.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6292-425x-ff64

## What is CVE-2016-7844?

CVE-2016-7844 is a medium-severity command injection vulnerability in WAM!NET Japan K.K. GigaCC OFFICE, published on 2 Aug 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

GigaCC OFFICE ver.2.3 and earlier allows remote attackers to execute arbitrary OS commands via specially crafted mail template.

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

## Which versions are affected by CVE-2016-7844?

It affects 1 product.


Products: Gigaccsecure Gigacc Office.

## How do I fix CVE-2016-7844?

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

## Is CVE-2016-7844 being exploited?

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

## Other vulnerabilities in WAM!NET Japan K.K. GigaCC OFFICE

- [CVE-2016-7845](https://insights.sbomify.com/CVE-2016-7845/): File upload in GigaCC OFFICE (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7844 and fix it if it is affected.

What it is: CVE-2016-7844 is a medium-severity command injection vulnerability in WAM!NET Japan K.K. GigaCC OFFICE, published on 2 Aug 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-7844 in the wild and no public exploit code.

Affected product: WAM!NET Japan K.K. GigaCC OFFICE. 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-2016-7844/ (Markdown: https://insights.sbomify.com/CVE-2016-7844/index.md)
```

## Sources

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

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