Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61685 high CVSS 7.5

SQL Injection in @fecommunity/reactpress (CVE-2026-61685)

Summary

SQL injection in @fecommunity/reactpress (CVE-2026-61685). Confidential information can be exposed externally. Exploitable via GET /api/article. Mitigation: upgrade to 3.7.0 or later.

Original description

The description as published by the source.

Summary

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.

Impact

An unauthenticated remote attacker can perform blind SQL injection against
the application database, potentially exfiltrating sensitive data (users,
settings, API keys, article content, etc.).

Affected endpoints (unauthenticated GET)

  • GET /api/article
  • GET /api/comment
  • GET /api/file
  • GET /api/page
  • GET /api/Knowledge

Affected code

Vulnerable pattern in findAll() methods, including but not limited to:

  • server/src/modules/article/article.service.ts
  • server/src/modules/comment/comment.service.ts
  • server/src/modules/file/file.service.ts
  • server/src/modules/page/page.service.ts
  • server/src/modules/knowledge/knowledge.service.ts

Remediation

  • Whitelist allowed filter column names before interpolating into SQL.
  • Upgrade to @fecommunity/reactpress >= 3.7.0.

Credit

Reported by lsr365400.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61685 has been found in @fecommunity/reactpress.
Attackers can target a specific entry point like GET /api/article over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade @fecommunity/reactpress to 3.7.0 or later.
If unsure, ask your IT team or search "@fecommunity/reactpress CVE-2026-61685" on the vendor's site.

CVE-2026-61685 (@fecommunity/reactpress) — CWE-89 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/article / GET /api/comment / GET /api/file / GET /api/page
Patched: 3.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in @fecommunity/reactpress. Attackers reach the vulnerable code path via GET /api/article without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @fecommunity/reactpress. Attack surface: GET /api/article / GET /api/comment / GET /api/file / GET /api/page.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.7.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/article requests with malformed payloads or SQL meta-characters. Run grep -r '@fecommunity/reactpress' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@fecommunity/reactpress' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @fecommunity/reactpress を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/article' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/article への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade @fecommunity/reactpress to 3.7.0

    ステージング環境で 3.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /api/article on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @fecommunity/reactpress
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details