CVE-2020-26877: n/a vulnerability

CVE-2020-26877: ApiFest OAuth 2.0 Server 0.3.1 does not validate the redirect URI in accordance with RFC 6749 and is suscep...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 4, 2024, 16:03 UTC (UTC+00:00)

Security readout for executives and security teams

ApiFest OAuth 2.0 Server 0.3.1 may send OAuth authorization codes to attacker-controlled redirect URLs. If an organization uses this server for login or authorization flows, a manipulated redirect could expose codes intended for legitimate clients. Exposure is limited to deployments using ApiFest OAuth 2.0 Server 0.3.1 in OAuth authorization-code flows. The source bundle does not provide CPEs or broader affected-version metadata. Treat as a targeted application-security risk, not a broad emergency. Prioritize review if ApiFest handles customer, employee, or partner authentication flows. Mitigation focus: Check the ApiFest project and vendor guidance for fixed versions or migration advice.; Require redirect_uri values to match URIs registered for the requesting client.; Avoid using ApiFest OAuth 2.0 Server 0.3.1 for authorization-code flows until remediated..

Prepared: Jun 2, 2026, 02:45 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-26877 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 29, 2022, 13:15 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://tools.ietf.org/html/rfc6749#section-3.1.2.3CVE reference · x_refsource_MISC
https://github.com/apifest/apifest-oauth20CVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.