# CVE-2022-2600: Auto-hyperlink URLs <= 5.4.1 - Tab Nabbing

> The Auto-hyperlink URLs WordPress plugin fails to set rel attributes, allowing tab-nabbing attacks via window.opener access.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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:** 22 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9j82-qgpc-g3mq

## What is CVE-2022-2600?

CVE-2022-2600 is a medium-severity vulnerability in Unknown Auto-hyperlink URLs, published on 22 Aug 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 Auto-hyperlink URLs WordPress plugin through 5.4.1 does not set rel="noopener noreferer" on generated links, which can lead to Tab Nabbing by giving the target site access to the source tab through the window.opener DOM object.

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

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

It affects 1 product.


Products: Auto-Hyperlink Urls Project Auto-Hyperlink Urls.

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

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

## Is CVE-2022-2600 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2600 is a medium-severity vulnerability in Unknown Auto-hyperlink URLs, published on 22 Aug 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-2600 in the wild and no public exploit code.

Affected product: Unknown Auto-hyperlink URLs. 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-2600/ (Markdown: https://insights.sbomify.com/CVE-2022-2600/index.md)
```

## Sources

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

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