CVE-2020-15270: Open Source Vulnerability in Parse Server

parse Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2020-15270: Improper session expiration in Parse Server. Affects parse versions < 4.3.1. Fixed in 4.3.1. How to fix ↓

Also tracked for

The same CVE-2020-15270 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Parse Server is an npm package that provides a backend framework for building scalable and flexible applications. It is commonly used in conjunction with Node.js. This vulnerability affects the Parse Server package, specifically the broadcast events functionality. The package allows events to be broadcasted to all clients without verifying the validity of the session token. This means that clients with expired sessions can still receive subscription objects. It is important to note that subscription objects cannot be created with invalid session tokens. The vulnerability has not been patched yet.

Vulnerability Detail

The vulnerability in Parse Server allows clients with expired sessions to continue receiving subscription objects. This can lead to unauthorized access to sensitive information or the execution of unauthorized actions. The issue arises from the lack of validation of session tokens when broadcasting events. As a result, clients with expired sessions are not properly filtered out. The severity of this vulnerability is considered medium, with a CVSS v3 score of 3.1. It is recommended to address this vulnerability promptly to prevent potential security breaches.

How To Fix

Minimum fixed version

4.3.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there is no known workaround for this vulnerability. It is essential to update the Parse Server package to the patched version to mitigate the risk.

Conclusion

The vulnerability in Parse Server allows clients with expired sessions to receive subscription objects, potentially leading to unauthorized access or actions. It is crucial to update the Parse Server package to version 4.3.0 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for parse →

Share this vulnerability

FAQ

Parse Server is an npm package that provides a backend framework for building scalable and flexible applications. It is commonly used with Node.js.

The vulnerability allows clients with expired sessions to continue receiving subscription objects, potentially leading to unauthorized access or unauthorized actions.

No, it is not possible to create subscription objects with invalid session tokens. The vulnerability only affects the broadcasting of events to clients with expired sessions.

The vulnerability is considered medium severity, with a CVSS v3 score of 3.1.

Yes, the vulnerability can be fixed by updating the Parse Server package to version 4.3.0 or later.

Related vulnerabilities

Recent vulnerabilities recorded for parse.

How To Fix

Minimum fixed version

4.3.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback