Security readout for executives and security teams
Plain-English summary
CVE-2018-1000088 is a stored XSS issue in Doorkeeper’s OAuth web views. A malicious OAuth client name could cause script execution when a user views the OAuth app form or authorization prompt. The sources say fixed releases are 4.2.6 and 4.3.0.
Executive priority
Treat this as a moderate web application security issue. It is not documented as actively exploited in the supplied sources, but OAuth authorization screens are trust-sensitive, and exposed vulnerable versions should be upgraded during the next security maintenance window.
Technical view
Doorkeeper versions 2.1.0 through 4.2.5 did not safely handle the OAuth client name in affected web views, allowing stored XSS. Exploitation requires a victim to follow a link to the affected web view and interact with content that renders the stored client name.
Likely exposure
Exposure is likely limited to applications using Doorkeeper 2.1.0 through 4.2.5 and exposing the affected OAuth app or authorization prompt web views. The bundle does not provide CPEs, CVSS, or broader affected product data.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. It describes user interaction: the victim must be tricked into clicking a link to a web view that renders the stored XSS payload.
Researcher notes
Evidence is limited but consistent: the CVE text identifies stored XSS in Doorkeeper OAuth web views, affected versions 2.1.0 through 4.2.5, user-click exploitation, and fixes in 4.2.6 and 4.3.0. No CVSS, CWE, CPE, or KEV evidence is provided.
Mitigation direction
- Upgrade Doorkeeper to 4.2.6, 4.3.0, or a later maintained version.
- Review registered OAuth client names for suspicious script-like content.
- Restrict who can create or rename OAuth clients.
- Check the Doorkeeper project guidance before applying compensating controls.
- Prioritize systems where OAuth consent screens are internet-facing.
Validation and detection
- Inventory deployed Doorkeeper gem versions across applications.
- Confirm no application runs Doorkeeper 2.1.0 through 4.2.5.
- Review OAuth client records for unsafe names or unexpected changes.
- Test affected web views after upgrade using benign XSS validation strings.
- Check logs for unusual OAuth client creation or rename activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2018-1000088 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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://github.com/rubysec/ruby-advisory-db/pull/328/filesCVE reference · x_refsource_MISC
- https://github.com/doorkeeper-gem/doorkeeper/issues/969CVE reference · x_refsource_MISC
- https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.3.0CVE reference · x_refsource_MISC
- https://github.com/doorkeeper-gem/doorkeeper/pull/970CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
