How severe is CVE-2020-10187?

CVE-2020-10187 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2020-10187 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-10187?

CVE-2020-10187 affects Doorkeeper Project Doorkeeper. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-10187?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-10187 published?

CVE-2020-10187 was published on 2020-05-04 and last updated on 2026-06-17.

CVE-2020-10187

CVE-2020-10187 is a high-severity vulnerability in Doorkeeper Project Doorkeeper with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-862.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 4.3
EPSS exploit prediction: 2% (79th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-862
Affected product: Doorkeeper Project Doorkeeper
Published: 2020-05-04
Last modified: 2026-06-17

Description

Doorkeeper version 5.0.0 and later contains an information disclosure vulnerability that allows an attacker to retrieve the client secret only intended for the OAuth application owner. After authorizing the application and allowing access, the attacker simply needs to request the list of their authorized applications in a JSON format (usually GET /oauth/authorized_applications.json). An application is vulnerable if the authorized applications controller is enabled.

Frequently asked questions

What is CVE-2020-10187?: Doorkeeper version 5.0.0 and later contains an information disclosure vulnerability that allows an attacker to retrieve the client secret only intended for the OAuth application owner. After authorizing the application and allowing access, the attacker simply needs to request the list of their authorized applications in a JSON format (usually GET /oauth/authorized_applications.json). An application is vulnerable if the authorized applications controller is enabled.
How severe is CVE-2020-10187?: CVE-2020-10187 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2020-10187 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-10187?: CVE-2020-10187 affects Doorkeeper Project Doorkeeper. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-10187?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-10187 published?: CVE-2020-10187 was published on 2020-05-04 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:doorkeeper_project:doorkeeper:*:*:*:*:*:ruby:*:*

More vulnerabilities in Doorkeeper Project Doorkeeper

CVE-2016-6582 — Critical (CVSS 9.1): The Doorkeeper gem before 4.2.0 for Ruby might allow remote attackers to conduct replay attacks or revoke arbitrary…
CVE-2018-1000211 — High (CVSS 7.5): Doorkeeper version 4.2.0 and later contains a Incorrect Access Control vulnerability in Token revocation API's…
CVE-2014-8144 — Medium (CVSS 6.8): Cross-site request forgery (CSRF) vulnerability in doorkeeper before 1.4.1 allows remote attackers to hijack the…
CVE-2018-1000088 — Medium (CVSS 6.1): Doorkeeper version 2.1.0 through 4.2.5 contains a Cross Site Scripting (XSS) vulnerability in web view's OAuth app…
CVE-2023-34246 — Medium (CVSS 4.2): Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape. Prior to version 5.6.6, Doorkeeper automatically processes…

All CVEs affecting Doorkeeper Project Doorkeeper →

Other CWE-862 (Missing Authorization) vulnerabilities

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2026-33712 — Critical (CVSS 10.0): Typebot is a chatbot builder tool. In versions 3.15.2 and prior, the preview chat endpoint (POST…
CVE-2026-2031 — Critical (CVSS 10.0): An Improper Access Control vulnerability in several internal API endpoints for Google Cloud Application Integration…
CVE-2026-34976 — Critical (CVSS 10.0): Dgraph is an open source distributed GraphQL database. Prior to 25.3.1, the restoreTenant admin mutation is missing…
CVE-2025-30416 — Critical (CVSS 10.0): Sensitive data disclosure and manipulation due to missing authorization. The following products are affected: Acronis…
CVE-2025-45854 — Critical (CVSS 10.0): /server/executeExec of JEHC-BPM 2.0.1 allows attackers to execute arbitrary code via execParams.

Browse all CWE-862 (Missing Authorization) vulnerabilities →