# CVE-2022-33146: Open redirect in web2py

> Remote attackers can redirect users to malicious sites via crafted URLs, facilitating phishing attacks against web2py users.

- **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:** Yes
- **Published:** 27 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cgrj-xjm7-9q27, PYSEC-2026-1060, UBUNTU-CVE-2022-33146

## What is CVE-2022-33146?

CVE-2022-33146 is a medium-severity vulnerability in web2py, published on 27 Jun 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

Open redirect vulnerability in web2py versions prior to 2.22.5 allows a remote attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having a user to access a specially crafted URL.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

3 open source packages ship an affected version, including web2py. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `web2py` | PyPI | All versions | 2.22.5 |
| `web2py` | PyPI | All versions | 2.22.5 |
| `web2py` | PyPI | All versions | 2.22.5 |

Products: Web2py Web2py.

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

Upgrade web2py to 2.22.5 or later.

## Is CVE-2022-33146 being exploited?

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

## Other vulnerabilities in web2py

- [CVE-2023-45158](https://insights.sbomify.com/CVE-2023-45158/): Command injection in web2py (critical 9.8)
- [CVE-2016-3953](https://insights.sbomify.com/CVE-2016-3953/): web2py remote code execution via hardcoded encryption key in session.connect function (critical 9.8)
- [CVE-2016-3957](https://insights.sbomify.com/CVE-2016-3957/): Deserialization in n/a (critical 9.8)
- [CVE-2016-10321](https://insights.sbomify.com/CVE-2016-10321/): web2py is vulnerable to password brute-force attack (critical 9.8)
- [CVE-2016-4808](https://insights.sbomify.com/CVE-2016-4808/): Web2py Cross-Site Request Forgery vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33146 is a medium-severity vulnerability in web2py, published on 27 Jun 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-33146 in the wild and no public exploit code.

Affected packages and fixed versions:
- web2py (PyPI): affected all versions; fixed in 2.22.5
- web2py (PyPI): affected all versions; fixed in 2.22.5
- web2py (PyPI): affected all versions; fixed in 2.22.5

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-33146/ (Markdown: https://insights.sbomify.com/CVE-2022-33146/index.md)
```

## Sources

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

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