VulnerabilityPublished 31 Mar 2024Updated 8 Sep 2026

CVE-2024-27298: Parse Server literalizeRegexPart SQL Injection

Affects parseSource GCVE Database

Not known to be exploited : upgrade to 6.5.0 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

Severity

Critical

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.5.0

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade parse to 6.5.0.

Patches and advisories

Affected software

Product	Affected	Fixed in
Bitnamiparse`pkg:bitnami/parse`Other threats	Affected <6.5.0	Fixed in 6.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade parse-server to version 6.5.0 or later, or 7.0.0 or later, where this vulnerability has been fixed. Applying these official patches fully mitigates the risk. No additional mitigation steps are required if the upgrade is applied.

Description

Parse Server for Node.js / Express contains a critical SQL injection vulnerability (CVE-2024-27298) affecting configurations using PostgreSQL. This flaw allows SQL injection attacks via the literalizeRegexPart component. The issue has been fixed in versions 6.5.0 and 7.0.0.

Impact

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary SQL commands on the PostgreSQL database used by parse-server, potentially leading to unauthorized data access, modification, or deletion. The severity is critical given the nature of SQL injection vulnerabilities and their impact on data security.

Summary

The vulnerability in parse-server arises when it is configured to use PostgreSQL as the database backend. An SQL injection flaw exists in the literalizeRegexPart functionality, enabling attackers to inject malicious SQL commands. This vulnerability is critical due to the potential impact on database integrity and confidentiality. The issue has been addressed and fixed in parse-server versions 6.5.0 and 7.0.0.

References

Community reviews

Loading reviews…