Security Digest · Vulnerability record

CVE-2024-39309: ZDI-CAN-23894: Parse Server literalizeRegexPart SQL Injection Authentication Bypass Vulnerability

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js.

CVSS 9.8 Critical EPSS 20.2% · p97

Should you act?

High exploit likelihood

EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 20.2%, percentile 97: FIRST’s model estimates a 20.2% chance of exploitation activity in the next 30 days, higher than 97% of all scored CVEs (very high). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes parse-server (npm) < 6.5.7, fixed in 6.5.7; parse-server (npm) >= 7.0.0, < 7.1.0, fixed in 7.1.0. Check your lockfile, including transitive dependencies.

What it is

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. A vulnerability in versions prior to 6.5.7 and 7.1.0 allows SQL injection when Parse Server is configured to use the PostgreSQL database. The algorithm to detect SQL injection has been improved in versions 6.5.7 and 7.1.0. No known workarounds are available.

From the GitHub advisory

Impact

This vulnerability allows SQL injection when Parse Server is configured to use the PostgreSQL database.

Patches

The algorithm to detect SQL injection has been improved.

Workarounds

Weakness type: CWE-288, CWE-89.

Product: parse-server (npm) · Assigned by: GitHub_M · Published: 2024-07-01

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
npmparse-server< 6.5.76.5.7
npmparse-server>= 7.0.0, < 7.1.07.1.0
VendorProductAffected versions (per CVE record)
parse-communityparse-server< 6.5.7, >= 7.0.0, < 7.1.0

Severity scores

Scored byCVSSScoreVector
GitHub_M3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub3.19.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 20.17% probability of exploitation activity in the next 30 days; percentile 97.

Timeline

  • — CVE record published by GitHub_M
  • — GitHub-reviewed advisory GHSA-c2hr-cqg6-8j6r published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-c2hr-cqg6-8j6r github.com
  2. CVE.org record CVE-2024-39309 cve.org
  3. NVD entry CVE-2024-39309 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com
  5. github.com github.com

Critical npm advisories · Today’s Security Digest