CVE-2025-68150: CWE-918: Server-Side Request Forgery (SSRF) in parse-community parse-server
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.2 and 9.1.1-alpha.1, the Instagram authentication adapter allows clients to specify a custom API URL via the `apiURL` parameter in `authData`. This enables SSRF attacks and possibly authentication bypass if malicious endpoints return fake responses to validate unauthorized users. This is fixed in versions 8.6.2 and 9.1.1-alpha.1 by hardcoding the Instagram Graph API URL `https://graph.instagram.com` and ignoring client-provided `apiURL` values. No known workarounds are available.
AI Analysis
Technical Summary
CVE-2025-68150 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918 found in the parse-community's parse-server open-source backend framework. The vulnerability exists in the Instagram authentication adapter prior to versions 8.6.2 and 9.1.1-alpha.1, where the adapter accepts a client-supplied apiURL parameter within the authData object. This parameter allows an attacker to specify arbitrary API endpoints, enabling SSRF attacks by making the server send HTTP requests to unintended internal or external resources. SSRF can be leveraged to access internal services that are otherwise inaccessible externally, potentially exposing sensitive data or internal network infrastructure. Furthermore, the vulnerability may allow authentication bypass if the attacker controls the malicious endpoint and returns crafted responses that the server interprets as valid Instagram authentication responses, thus granting unauthorized access. The vulnerability is remotely exploitable over the network without user interaction but requires limited privileges (PR:L), indicating that some level of authenticated access or API interaction is needed. The fix implemented in versions 8.6.2 and 9.1.1-alpha.1 hardcodes the Instagram Graph API URL (https://graph.instagram.com) and ignores any client-provided apiURL values, effectively eliminating the SSRF vector. No known workarounds exist, and no public exploits have been reported at the time of publication. The CVSS v4.0 score is 8.3 (high severity), reflecting the potential for significant impact on confidentiality and integrity without requiring user interaction. Organizations using parse-server with Instagram authentication on vulnerable versions should prioritize upgrading to patched versions to mitigate this risk.
Potential Impact
For European organizations, this vulnerability poses a significant risk especially for those deploying parse-server as part of their backend infrastructure with Instagram authentication enabled. SSRF can be exploited to access internal network resources, potentially exposing sensitive internal services, configuration data, or cloud metadata endpoints. This could lead to data breaches, lateral movement within networks, or further exploitation. The authentication bypass possibility increases the risk by allowing attackers to impersonate legitimate users, leading to unauthorized access to protected resources or services. Industries relying on parse-server for customer-facing applications, such as e-commerce, social platforms, or SaaS providers, are particularly vulnerable. The lack of user interaction requirement and network-level exploitability means attackers can automate attacks remotely. The impact on confidentiality and integrity is high, while availability impact is limited. Given the widespread use of Node.js and open-source backend frameworks in Europe, the threat could affect a broad range of organizations, including SMEs and large enterprises.
Mitigation Recommendations
The primary mitigation is to upgrade parse-server to version 8.6.2 or later, or 9.1.1-alpha.1 or later, where the vulnerability is fixed by hardcoding the Instagram Graph API URL. Organizations should audit their parse-server deployments to identify affected versions and Instagram authentication usage. If immediate upgrade is not feasible, restrict network egress from parse-server instances to only allow connections to trusted Instagram API endpoints, effectively limiting SSRF exploitation. Implement network-level monitoring and alerting for unusual outbound requests originating from parse-server hosts. Review authentication logs for suspicious activity indicative of authentication bypass attempts. Employ web application firewalls (WAFs) with SSRF detection capabilities to block malicious requests. Additionally, conduct internal penetration testing focusing on SSRF vectors in parse-server integrations. Finally, maintain an inventory of all backend services using parse-server and ensure timely patch management processes are in place to address future vulnerabilities.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain
CVE-2025-68150: CWE-918: Server-Side Request Forgery (SSRF) in parse-community parse-server
Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.2 and 9.1.1-alpha.1, the Instagram authentication adapter allows clients to specify a custom API URL via the `apiURL` parameter in `authData`. This enables SSRF attacks and possibly authentication bypass if malicious endpoints return fake responses to validate unauthorized users. This is fixed in versions 8.6.2 and 9.1.1-alpha.1 by hardcoding the Instagram Graph API URL `https://graph.instagram.com` and ignoring client-provided `apiURL` values. No known workarounds are available.
AI-Powered Analysis
Technical Analysis
CVE-2025-68150 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918 found in the parse-community's parse-server open-source backend framework. The vulnerability exists in the Instagram authentication adapter prior to versions 8.6.2 and 9.1.1-alpha.1, where the adapter accepts a client-supplied apiURL parameter within the authData object. This parameter allows an attacker to specify arbitrary API endpoints, enabling SSRF attacks by making the server send HTTP requests to unintended internal or external resources. SSRF can be leveraged to access internal services that are otherwise inaccessible externally, potentially exposing sensitive data or internal network infrastructure. Furthermore, the vulnerability may allow authentication bypass if the attacker controls the malicious endpoint and returns crafted responses that the server interprets as valid Instagram authentication responses, thus granting unauthorized access. The vulnerability is remotely exploitable over the network without user interaction but requires limited privileges (PR:L), indicating that some level of authenticated access or API interaction is needed. The fix implemented in versions 8.6.2 and 9.1.1-alpha.1 hardcodes the Instagram Graph API URL (https://graph.instagram.com) and ignores any client-provided apiURL values, effectively eliminating the SSRF vector. No known workarounds exist, and no public exploits have been reported at the time of publication. The CVSS v4.0 score is 8.3 (high severity), reflecting the potential for significant impact on confidentiality and integrity without requiring user interaction. Organizations using parse-server with Instagram authentication on vulnerable versions should prioritize upgrading to patched versions to mitigate this risk.
Potential Impact
For European organizations, this vulnerability poses a significant risk especially for those deploying parse-server as part of their backend infrastructure with Instagram authentication enabled. SSRF can be exploited to access internal network resources, potentially exposing sensitive internal services, configuration data, or cloud metadata endpoints. This could lead to data breaches, lateral movement within networks, or further exploitation. The authentication bypass possibility increases the risk by allowing attackers to impersonate legitimate users, leading to unauthorized access to protected resources or services. Industries relying on parse-server for customer-facing applications, such as e-commerce, social platforms, or SaaS providers, are particularly vulnerable. The lack of user interaction requirement and network-level exploitability means attackers can automate attacks remotely. The impact on confidentiality and integrity is high, while availability impact is limited. Given the widespread use of Node.js and open-source backend frameworks in Europe, the threat could affect a broad range of organizations, including SMEs and large enterprises.
Mitigation Recommendations
The primary mitigation is to upgrade parse-server to version 8.6.2 or later, or 9.1.1-alpha.1 or later, where the vulnerability is fixed by hardcoding the Instagram Graph API URL. Organizations should audit their parse-server deployments to identify affected versions and Instagram authentication usage. If immediate upgrade is not feasible, restrict network egress from parse-server instances to only allow connections to trusted Instagram API endpoints, effectively limiting SSRF exploitation. Implement network-level monitoring and alerting for unusual outbound requests originating from parse-server hosts. Review authentication logs for suspicious activity indicative of authentication bypass attempts. Employ web application firewalls (WAFs) with SSRF detection capabilities to block malicious requests. Additionally, conduct internal penetration testing focusing on SSRF vectors in parse-server integrations. Finally, maintain an inventory of all backend services using parse-server and ensure timely patch management processes are in place to address future vulnerabilities.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-15T20:13:34.486Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6941a4041a61eff6269a9348
Added to database: 12/16/2025, 6:25:08 PM
Last enriched: 12/16/2025, 6:40:27 PM
Last updated: 12/17/2025, 1:19:01 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-53524: CWE-787 in Fuji Electric Monitouch V-SFT-6
HighCVE-2025-14701: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Arcadia Technology, LLC Crafty Controller
HighCVE-2025-14700: CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine in Arcadia Technology, LLC Crafty Controller
CriticalCVE-2025-14766: Out of bounds read and write in Google Chrome
UnknownCVE-2025-14765: Use after free in Google Chrome
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.