Unrestricted File Upload in baserproject/basercms (CVE-2020-15277)
Summary
Vulnerability in baserproject/basercms (CVE-2020-15277). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.4.1 or later.
Original description
The description as published by the source.
baserCMS 4.4.0 and earlier is affected by Remote Code Execution (RCE).
Impact: XSS via Arbitrary script execution.
Attack vector is: Administrator must be logged in.
Components are: Edit template.
Tested baserCMS Version : 4.4.0 (Latest)
Affected baserCMS Version : 4.0.0 ~ 4.4.0
Patches : https://basercms.net/security/20201029
Found by Aquilao Null
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-2020-15277 has been found in baserproject/basercms.
Successful exploitation can lead to full system takeover.
What to do: upgrade baserproject/basercms to 4.4.1 or later.
If unsure, ask your IT team or search "baserproject/basercms CVE-2020-15277" on the vendor's site.
CVE-2020-15277 (baserproject/basercms) — CWE-434
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.4.1 — 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-434) exists in baserproject/basercms.
Check the vendor advisory for the affected versions of baserproject/basercms.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 4.4.1.
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. Run grep -r 'baserproject/basercms' . 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 'baserproject/basercms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
baserproject/basercmsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade baserproject/basercms to 4.4.1ステージング環境で 4.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web basercms.net