Security readout for executives and security teams
Plain-English summary
Parse Server could label a new anonymous REST session as created with a password. If an application trusted that label to grant stronger access, anonymous users could be treated like password users. Parse Server itself does not use the label internally, so risk is limited to custom application logic.
Executive priority
Prioritize remediation where anonymous login is enabled and custom authorization depends on session metadata. Otherwise, treat as a contained medium-risk library update.
Technical view
Before 4.5.1, REST anonymous signup populated _Session.createdWith.authProvider as password. The issue is CWE-287 with CVSS 4.8. Affected software is parse-server below 4.5.1. Impact depends on developers directly using createdWith for authorization or trust decisions.
Likely exposure
Exposure is likely in Parse Server deployments below 4.5.1 that allow anonymous login and directly use _Session.createdWith to distinguish anonymous and password sessions.
Exploitation context
The bundle provides no KEV listing or active exploitation evidence. The advisory says Parse Server internal functions do not rely on createdWith, so exploitation requires application-specific logic that trusts this session field.
Researcher notes
The core defect is incorrect session metadata, not a documented server-side authorization bypass. Validate exposure by tracing application use of createdWith. Do not assume impact without proving business logic trusts that field.
Mitigation direction
- Upgrade Parse Server to version 4.5.1 or later.
- Stop using _Session.createdWith for access decisions.
- Review vendor advisory and 4.5.1 release notes.
- Audit custom authorization logic around anonymous users.
- Add tests for anonymous versus password-user access boundaries.
Validation and detection
- Inventory deployed parse-server versions and confirm 4.5.1 or later.
- Confirm whether anonymous login is enabled.
- Search application code for _Session.createdWith or authProvider checks.
- Review access-control tests covering anonymous sessions.
- Verify production deployments use the patched package version.
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.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-39138 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
- Medium
- CVSS
- 4.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N2.22.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/parse-community/parse-server/security/advisories/GHSA-23r4-5mxp-c7g5CVE reference · x_refsource_CONFIRM
- https://github.com/parse-community/parse-server/commit/147bd9a3dc43391e92c36e05d5db860b04ca27dbCVE reference · x_refsource_MISC
- https://github.com/parse-community/parse-server/releases/tag/4.5.1CVE 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.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
