# CVE-2019-12134: Other in n/a

> Attackers can execute arbitrary commands on victims' machines by injecting malicious formulas into CSV exports generated by Workday.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 6 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-99wc-g6xm-mv9h

## What is CVE-2019-12134?

CVE-2019-12134 is a high-severity vulnerability in n/a, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CSV Injection (aka Excel Macro Injection or Formula Injection) exists in the export feature in Workday through 32 via a value (provided by a low-privileged user in a contact form field) that is mishandled in a CSV export.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

## Which versions are affected by CVE-2019-12134?

It affects 1 product.


Products: Workday Workday.

## How do I fix CVE-2019-12134?

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

## Is CVE-2019-12134 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12134 and fix it if it is affected.

What it is: CVE-2019-12134 is a high-severity vulnerability in n/a, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12134 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-2019-12134/ (Markdown: https://insights.sbomify.com/CVE-2019-12134/index.md)
```

## Sources

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

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