Vulnerability in Chyrp Lite (CVE-2026-35173)
Summary
Vulnerability in Chyrp Lite (CVE-2026-35173). Data can be tampered with by attackers. Mitigation: upgrade to 2026.01 or later.
Original description
The description as published by the source.
Chyrp Lite is an ultra-lightweight blogging engine. Prior to 2026.01, an IDOR / Mass Assignment issue exists in the Post model that allows authenticated users with post editing permissions (Edit Post, Edit Draft, Edit Own Post, Edit Own Draft) to modify posts they do not own and do not have permission to edit. By passing internal class properties such as id into the post_attributes payload, an attacker can alter the object being instantiated. As a result, further actions are performed on another user’s post rather than the attacker’s own post, effectively enabling post takeover. This vulnerability is fixed in 2026.01.
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-35173 has been found in Chyrp Lite.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade Chyrp Lite to 2026.01 or later.
If unsure, ask your IT team or search "Chyrp Lite CVE-2026-35173" on the vendor's site.
CVE-2026-35173 (Chyrp Lite) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.01 — 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.
A vulnerability (CWE-639) exists in Chyrp Lite.
Check the vendor advisory for the affected versions of Chyrp Lite.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 2026.01.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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・依存マニフェストで Chyrp Lite を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Chyrp Lite to 2026.01ステージング環境で 2026.01 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov