Code Injection in Flextype CMS (CVE-2026-77939)
Summary
Code injection in Flextype CMS (CVE-2026-77939). Confidential information can be exposed externally. Exploitable via POST /api/v1/query.
Original description
The description as published by the source.
Flextype CMS through v1.0.0-dev contains an expression language injection vulnerability that allows authenticated attackers with a valid API token to read arbitrary files by passing unsanitized user-supplied input to the Symfony ExpressionLanguage engine via the POST /api/v1/query endpoint. Attackers can leverage exposed application objects including filesystem() and serializers() within the evaluation scope to read arbitrary server files and achieve conditional remote code execution if a PHP file can be placed on disk through a secondary vector.
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-77939 has been found in Flextype CMS.
Attackers can target a specific entry point like POST /api/v1/query over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Flextype CMS CVE-2026-77939" on the vendor's site.
CVE-2026-77939 (Flextype CMS) — CWE-94 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/query
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.
Arbitrary code execution (CWE-94) exists in Flextype CMS. Attackers reach the vulnerable code path via POST /api/v1/query.
Check the vendor advisory for the affected versions of Flextype CMS. Attack surface: POST /api/v1/query.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
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/v1/query 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・依存マニフェストで Flextype CMS を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /api/v1/query' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/queryへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/v1/query on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com