CVE-2020-5233

What it is

OAuth2 Proxy before 5.0 has an open redirect vulnerability. Authentication tokens could be silently harvested by an attacker. This has been patched in version 5.0.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. High risk of data tampering.

Exploit odds

1.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-01-30 19:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:21 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.3% in the next 30 days (EPSS).
• Severity: 5.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-01-30 19:15 UTC

Last modified

2026-06-17 03:21 UTC

Exploit probability

1.3% · EPSS, next 30 days

Weakness

CWE-601

Record status

Modified

Affected

• oauth2 Proxy Project oauth2 Proxy < 5.0.0

Attack profile CVSS 3.1 · 5.9

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

High

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-5233.md and follow it. Check whether this project is affected by CVE-2020-5233. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge