# CVE-2019-6979: Cross-site scripting in n/a

> Cross-site scripting in MyBB IP History Logs plugin allows attackers to inject scripts via the useragent field, potentially compromising admin sessions.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 28 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w3q6-7cqg-7vxc

## What is CVE-2019-6979?

CVE-2019-6979 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Jan 2019. 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

An issue was discovered in the User IP History Logs (aka IP_History_Logs) plugin 1.0.2 for MyBB. There is XSS via the admin/modules/tools/ip_history_logs.php useragent field.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Ip History Logs Project Ip History Logs.

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

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

## Is CVE-2019-6979 being exploited?

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

Public exploit code:

- MyBB IP History Logs Plugin 1.0.2 - Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6979 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Jan 2019. 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-2019-6979 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-6979/ (Markdown: https://insights.sbomify.com/CVE-2019-6979/index.md)
```

## Sources

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

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