# CVE-2018-1028: Code injection in Excel

> Attackers can execute arbitrary code by tricking users into opening Office documents with malicious embedded fonts.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-87hq-2c3x-p62g

## What is CVE-2018-1028?

CVE-2018-1028 is a high-severity code injection vulnerability in Microsoft Office, published on 12 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A remote code execution vulnerability exists when the Office graphics component improperly handles specially crafted embedded fonts, aka "Microsoft Office Graphics Remote Code Execution Vulnerability." This affects Word, Microsoft Office, Microsoft SharePoint, Excel, Microsoft SharePoint Server.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2018-1028?

It affects 6 products.


Products: Microsoft Excel Services, Microsoft Office, Microsoft Office 2010, Microsoft Office Web Apps, Microsoft Sharepoint Enterprise Server, Microsoft Word Automation Services.

## How do I fix CVE-2018-1028?

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

## Is CVE-2018-1028 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1028 and fix it if it is affected.

What it is: CVE-2018-1028 is a high-severity code injection vulnerability in Microsoft Office, published on 12 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1028 in the wild and no public exploit code.

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

## Sources

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

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