Vulnerability in Bludit CMS (CVE-2026-38329)
Summary
Vulnerability in Bludit CMS (CVE-2026-38329). Successful exploitation can lead to full system takeover. Exploitable via POST /api/files/{key}.
Original description
The description as published by the source.
Bludit CMS before version 3.18.4 allows Remote Code Execution (RCE) via the API Plugin. The POST /api/files/{key} endpoint in bl-plugins/api/plugin.php fails to perform authorization checks and lacks file extension validation. An attacker with a valid API token can upload a malicious PHP script and execute arbitrary code on the server.
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-38329 has been found in Bludit CMS.
Attackers can target a specific entry point like POST /api/files/{key} over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Bludit CMS CVE-2026-38329" on the vendor's site.
CVE-2026-38329 (Bludit CMS) — CWE-862 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/files/{key}
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.
A vulnerability (CWE-862) exists in Bludit CMS. Attackers reach the vulnerable code path via POST /api/files/{key} without authentication.
Check the vendor advisory for the affected versions of Bludit CMS. Attack surface: POST /api/files/{key}.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/files/{key} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Bludit CMS を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /api/files/{key}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/files/{key}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/files/{key} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web gist.github.com
- web nvd.nist.gov
- web github.com