Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-56290 CISA KEV critical CVSS 9.8

[KEV] Unrestricted File Upload in Joomlack page-builder-ck (CVE-2026-56290)

Summary

vulnerability in Joomlack page-builder-ck (CVE-2026-56290). Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-56290** has been found in Joomlack page-builder-ck. Successful exploitation can lead to full system takeover. CVSS score: 9.8/10. Note: CISA has officially confirmed this is **actively exploited in the wild**. Treat it with elevated urgency. What to do: apply the vendor's official patched release. If unsure, ask your IT team or search "Joomlack page-builder-ck CVE-2026-56290" on the vendor's site.
CVE-2026-56290 (Joomlack page-builder-ck) — CWE-434 / CVSS v3 9.8 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Listed in CISA KEV — actively exploited, treat as top priority. 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
**A vulnerability** (CWE-434) exists in Joomlack page-builder-ck.
📍 Affected scope
Joomlack page-builder-ck — .
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover **Listed in CISA KEV** — actively exploited in the wild, treat as top priority.
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 request patterns matching this CVE's known IOCs. Run `grep -r 'page-builder-ck' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

  1. 1
    Identify exposure identify 
    grep -r 'page-builder-ck' . | grep -v node_modules

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

  2. 4
    Consider incident declaration escalate 
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

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

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →