Code Injection in github.com/plentico/plenti (CVE-2025-26260)
Summary
Code injection in github.com/plentico/plenti (CVE-2025-26260). Risk of unauthorized operations or information disclosure. Exploitable via POST /postlocal. Mitigation: upgrade to 0.7.17 or later.
Original description
The description as published by the source.
Plenti <= 0.7.16 is vulnerable to code execution. Users uploading '.svelte' files with the /postLocal endpoint can define the file name as javascript codes. The server executes the uploaded file name in host, and cause code execution.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2025-26260 has been found in github.com/plentico/plenti.
Attackers can target a specific entry point like POST /postlocal over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/plentico/plenti to 0.7.17 or later.
If unsure, ask your IT team or search "github.com/plentico/plenti CVE-2025-26260" on the vendor's site.
CVE-2025-26260 (github.com/plentico/plenti) — CWE-94
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /postlocal
Patched: 0.7.17 — 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.
Arbitrary code execution (CWE-94) exists in github.com/plentico/plenti. Attackers reach the vulnerable code path via POST /postlocal.
Check the vendor advisory for the affected versions of github.com/plentico/plenti. Attack surface: POST /postlocal.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.7.17.
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 /postlocal requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/plentico/plenti' . 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
-
1Identify exposure identify
grep -r 'github.com/plentico/plenti' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/plentico/plentiを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /postlocal' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /postlocalへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/plentico/plenti to 0.7.17ステージング環境で 0.7.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /postlocal on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web ahmetakan.com
- web github.com
- web github.com
- web pkg.go.dev
- web pkg.go.dev
- web ahmetakan.com