# CVE-2021-41657: Cross-site request forgery in n/a

> An attacker can perform clickjacking attacks against the SmartBear CodeCollaborator web UI, potentially tricking users into unintended actions.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 7 Mar 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-q65h-82xf-g836

## What is CVE-2021-41657?

CVE-2021-41657 is a medium-severity vulnerability in n/a, published on 7 Mar 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

SmartBear CodeCollaborator v6.1.6102 was discovered to contain a vulnerability in the web UI which would allow an attacker to conduct a clickjacking attack.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

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

It affects 1 product.


Products: Smartbear Collaborator.

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

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

## Is CVE-2021-41657 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26118](https://insights.sbomify.com/CVE-2020-26118/): Deserialization in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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