Cross-Site Scripting (XSS) in baserproject/basercms (CVE-2020-15273)
Summary
Cross-site scripting in baserproject/basercms (CVE-2020-15273). Confidential information can be exposed externally. Mitigation: upgrade to 4.4.1 or later.
Original description
The description as published by the source.
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. The issue affects the following components: Edit feed settings, Edit widget area, Sub site new registration, New category registration. Arbitrary JavaScript may be executed by entering specific characters in the account that can access the file upload function category list, subsite setting list, widget area edit, and feed list on the management screen. The issue was introduced in version 4.0.0. It is fixed in version 4.4.1.
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-15273 has been found in baserproject/basercms.
Confidential information can be exposed externally.
What to do: upgrade baserproject/basercms to 4.4.1 or later.
If unsure, ask your IT team or search "baserproject/basercms CVE-2020-15273" on the vendor's site.
CVE-2020-15273 (baserproject/basercms) — CWE-79
Attack vector: remote (network-reachable)
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.
Cross-site scripting (XSS) (CWE-79) exists in baserproject/basercms.
Check the vendor advisory for the affected versions of baserproject/basercms.
Severity: ?. Confidential information can be exposed externally.
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
- advisory packagist.org
- patch github.com
- patch github.com