Skip to main content
VulnerabilityPublished

CVE-2026-61685: fecommunity reactpress · SQL Injection

Affects fecommunity reactpressSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 3.7.0 soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.7.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade reactpress and fecommunity/reactpress to 3.7.0.

Affected software

ProductAffectedFixed in
fecommunityreactpressAffected
  • <3.7.0
Fixed in
  • 3.7.0
GitHubfecommunity/reactpresspkg:github/fecommunity/reactpressOther threatsAffected
  • <3.7.0
Fixed in
  • 3.7.0

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

AI-suggested

Upgrade ReactPress to version 3.7.0 or later, which contains an official patch addressing this SQL injection vulnerability. As a temporary workaround, implement an allowlist of permitted filter column names before interpolating them into SQL queries to prevent injection via crafted query string keys.

Description

ReactPress is a publishing system for React developers. Prior to version 3.7.0, ReactPress API list endpoints build TypeORM `QueryBuilder` conditions using unsanitized HTTP query parameter names as SQL column identifiers (e.g. `` `article.${key}` ``). TypeORM parameterizes values but not column names, allowing unauthenticated attackers to inject SQL through crafted query string keys. Version 3.7.0 contains a patch. As a workaround, allowlist allowed filter column names before interpolating into SQL.

References

Community reviews

Loading reviews…