# CVE-2019-6780: Open redirect in n/a

> The Wise Chat plugin for WordPress fails to secure external links, allowing attackers to exploit open redirects via missing noopener and noreferrer attributes.

- **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:** 24 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6432-c556-jjq9

## What is CVE-2019-6780?

CVE-2019-6780 is a medium-severity vulnerability in n/a, published on 24 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

The Wise Chat plugin before 2.7 for WordPress mishandles external links because rendering/filters/post/WiseChatLinksPostFilter.php omits noopener and noreferrer.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Kaine Wise Chat.

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

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

## Is CVE-2019-6780 being exploited?

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

Public exploit code:

- WordPress Plugin Wisechat 2.6.3 - Reverse Tabnabbing (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-32504](https://insights.sbomify.com/CVE-2023-32504/): WordPress Wise Chat Plugin <= 3.1.3 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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