CVE-2025-68150 json
Parse Server has Server-Side Request Forgery (SSRF) in Instagram OAuth Adapter
published 10mo ago modified 2mo ago also BIT-parse-2025-68150 , EUVD-2025-203837 , GHSA-3f5f-xgrj-97pf
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm parse-server 8.6.2, 9.1.1-alpha.1
- bitnami parse 8.6.2, 9.1.1
- parseplatform parse-server 8.6.2, 9.1.1-alpha.1
- parseplatform parse_server 8.6.2, 9.1.1-alpha.1
- github.com/parse-community/parse-server#9988 pull request
- github.com/parse-community/parse-server#9989 pull request
Is CVE-2025-68150 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10mo ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N |
| CNA | 4.0 | 8.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse-server | >=9.0.0, <9.1.1-alpha.1 <8.6.2 |
9.1.1-alpha.1 8.6.2 |
| bitnami | parse | <8.6.2 >=9.0.0, <9.1.1 |
8.6.2 9.1.1 |
Affected products
- parse-community parse-server
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/parse-community/parse-server/pull/9988
web, issue-tracking, patch
-
github.com
/parse-community/parse-server/pull/9989
web, issue-tracking, patch
-
github.com
/parse-community/parse-server/security/advisories/GHSA-3f5f-xgrj-97pf
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-68150
advisory, web
-
github.com
/parse-community/parse-server
package
Sources
- CVE List CVE-2025-68150
- GitHub Advisory GHSA-3f5f-xgrj-97pf
- NVD CVE-2025-68150
- OSV BIT-parse-2025-68150
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.