# CVE-2021-3337: Missing authorization in n/a

> Remote attackers can bypass content-reading restrictions in the Hide-Thread-Content plugin by clicking reply or quote links.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2486-f4hq-9m5c

## What is CVE-2021-3337?

CVE-2021-3337 is a high-severity missing authorization vulnerability in n/a, published on 28 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Hide-Thread-Content plugin through 2021-01-27 for MyBB allows remote attackers to bypass intended content-reading restrictions by clicking on reply or quote in the postbit.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2021-3337?

It affects 1 product.


Products: Hide Thread Content Project Hide Thread Content.

## How do I fix CVE-2021-3337?

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

## Is CVE-2021-3337 being exploited?

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

Public exploit code:

- MyBB Hide Thread Content Plugin 1.0 - Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3337 and fix it if it is affected.

What it is: CVE-2021-3337 is a high-severity missing authorization vulnerability in n/a, published on 28 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3337 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-2021-3337/ (Markdown: https://insights.sbomify.com/CVE-2021-3337/index.md)
```

## Sources

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

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