# CVE-1999-0750: Cross-site scripting in n/a

> Remote attackers can execute JavaScript via HTML STYLE tags in Hotmail, potentially taking over user accounts.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **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:** 4 Feb 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-9m65-8wpj-pvhx

## What is CVE-1999-0750?

CVE-1999-0750 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2000. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Hotmail allows Javascript to be executed via the HTML STYLE tag, allowing remote attackers to execute commands on the user's Hotmail account.

## Which versions are affected by CVE-1999-0750?

It affects 1 product.


Products: Microsoft Hotmail.

## How do I fix CVE-1999-0750?

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

## Is CVE-1999-0750 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0750 exists.

Public exploit code:

- Microsoft Internet Explorer 5 / Netscape Communicator 4.0/4.5/4.6 - JavaScript STYLE (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0081](https://insights.sbomify.com/CVE-2000-0081/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2000-0085](https://insights.sbomify.com/CVE-2000-0085/): Cross-site scripting in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0750 and fix it if it is affected.

What it is: CVE-1999-0750 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2000. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0750 exists.

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-1999-0750/ (Markdown: https://insights.sbomify.com/CVE-1999-0750/index.md)
```

## Sources

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

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