Vulnerability in civicrm (UBUNTU-CVE-2023-28447)
Summary
Vulnerability in civicrm (UBUNTU-CVE-2023-28447). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.7.1+dfsg-2ubuntu1+esm1 or later.
Original description
The description as published by the source.
Smarty is a template engine for PHP. In affected versions smarty did not properly escape javascript code. An attacker could exploit this vulnerability to execute arbitrary JavaScript code in the context of the user's browser session. This may lead to unauthorized access to sensitive user data, manipulation of the web application's behavior, or unauthorized actions performed on behalf of the user. Users are advised to upgrade to either version 3.1.48 or to 4.3.1 to resolve this issue. There are no known workarounds for this vulnerability.
Source: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2023-28447 has been found in civicrm.
Risk of unauthorized operations or information disclosure.
What to do: upgrade civicrm to 4.7.1+dfsg-2ubuntu1+esm1 or later.
If unsure, ask your IT team or search "civicrm UBUNTU-CVE-2023-28447" on the vendor's site.
UBUNTU-CVE-2023-28447 (civicrm)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 4.7.1+dfsg-2ubuntu1+esm1 — 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 (unclassified) exists in civicrm.
Check the vendor advisory for the affected versions of civicrm.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.7.1+dfsg-2ubuntu1+esm1.
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 'civicrm' . 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 'civicrm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
civicrmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade civicrm to 4.7.1+dfsg-2ubuntu1+esm1ステージング環境で 4.7.1+dfsg-2ubuntu1+esm1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report github.com
- report github.com
- report cve.org