# CVE-2022-1583: External Links in New Window / New Tab < 1.43 - Tabnabbing

> The WordPress plugin fails to nullify window.opener, allowing attackers to hijack the original tab via tabnabbing.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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:** 30 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fh98-fx6f-2pf6

## What is CVE-2022-1583?

CVE-2022-1583 is a medium-severity vulnerability in Unknown External Links in New Window / New Tab, published on 30 May 2022. 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 External Links in New Window / New Tab WordPress plugin before 1.43 does not ensure window.opener is set to "null" when links to external sites are clicked, which may enable tabnabbing attacks to occur.

Weakness: CWE-1022 (Use of Web Link to Untrusted Target with window.opener Access)

## Which versions are affected by CVE-2022-1583?

It affects 1 product.


Products: Webfactoryltd External Links in New Window \/ New Tab.

## How do I fix CVE-2022-1583?

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

## Is CVE-2022-1583 being exploited?

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

## Other vulnerabilities in Unknown External Links in New Window / New Tab

- [CVE-2022-1582](https://insights.sbomify.com/CVE-2022-1582/): External Links in New Window / New Tab < 1.43 - Unauthenticated Stored Cross-Site Scripting (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1583 and fix it if it is affected.

What it is: CVE-2022-1583 is a medium-severity vulnerability in Unknown External Links in New Window / New Tab, published on 30 May 2022. 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-2022-1583 in the wild and no public exploit code.

Affected product: Unknown External Links in New Window / New Tab. 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-2022-1583/ (Markdown: https://insights.sbomify.com/CVE-2022-1583/index.md)
```

## Sources

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

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