Read the docs
TI-2020-16307 Aliases CVE-2020-26877GHSA-hg6g-fgr6-h93g

ApiFest OAuth 2.0 Server 0.3.1 does not validate the redirect URI in accordance with RFC…

Priority LOW 29CWE-601Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Spoofing
Confidentiality · integrity · availability
Low · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-601.

Summary

ApiFest OAuth 2.0 Server 0.3.1 does not validate the redirect URI in accordance with RFC 6749 and is susceptible to an open redirector attack. Specifically, it directly sends an authorization code to the redirect URI submitted with the authorization request, without checking whether the redirect URI is registered by the client who initiated the request. This allows an attacker to craft a request with a manipulated redirect URI (redirect_uri parameter), which is under the attacker's control, and consequently obtain the leaked authorization code when the server redirects the client to the manipulated redirect URI with an authorization code. NOTE: this is similar to CVE-2019-3778.

Why it matters now

EPSS 0.0085 58th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:apifest:oauth_2.0_server:0.3.1:*:*:*:*:*:*:*0.3.1VulnerableApifest
  • cpe:2.3:a:apifest:oauth_2.0_server:0.3.1:*:*:*:*:*:*:* Versions 0.3.1 Vulnerable ·Apifest

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2020-26877
  2. 2026-10-03 Alias added: GHSA-hg6g-fgr6-h93g

References

Sources