# CVE-2020-5182: Other in n/a

> Attackers can exploit reverse tabnabbing in the J-BusinessDirectory extension if user-entered links lack security attributes, potentially hijacking user sessions.

- **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:** 3 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mvg4-g838-wp67

## What is CVE-2020-5182?

CVE-2020-5182 is a medium-severity vulnerability in n/a, published on 3 Feb 2020. 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 J-BusinessDirectory extension before 5.2.9 for Joomla! allows Reverse Tabnabbing. In some configurations, the link to the business website can be entered by any user. If it doesn't contain rel="noopener" (or similar attributes such as noreferrer), the tabnabbing may occur. To reproduce the bug, create a business with a website link that contains JavaScript to exploit the window.opener property (for example, by setting window.opener.location).

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2020-5182?

It affects 1 product.


Products: Cmsjunkie J-Businessdirectory.

## How do I fix CVE-2020-5182?

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

## Is CVE-2020-5182 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-25752](https://insights.sbomify.com/CVE-2019-25752/): Joomla! Component J-BusinessDirectory 4.9.7 SQL Injection (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-5182 and fix it if it is affected.

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

## Sources

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

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