Authorization Flaw in Masa CMS (CVE-2024-32643)
Summary
Vulnerability in Masa CMS (CVE-2024-32643). Confidential information can be exposed externally. Mitigation: upgrade to 7.2.8 or later.
Original description
The description as published by the source.
Masa CMS is an open source Enterprise Content Management platform. Prior to 7.2.8, 7.3.13, and 7.4.6, if the URL to the page is modified to include a /tag/ declaration, the CMS will render the page regardless of group restrictions. This vulnerability is fixed in 7.2.8, 7.3.13, and 7.4.6.
Source: NIST National Vulnerability Database NVD
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-2024-32643 has been found in Masa CMS.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade Masa CMS to 7.2.8 or later.
If unsure, ask your IT team or search "Masa CMS CVE-2024-32643" on the vendor's site.
CVE-2024-32643 (Masa CMS) — CWE-863 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.2.8 — 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.
Incorrect authorization (CWE-863) exists in Masa CMS.
Check the vendor advisory for the affected versions of Masa CMS.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 7.2.8.
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・依存マニフェストで Masa CMS を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Masa CMS to 7.2.8ステージング環境で 7.2.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com
- patch security-advisories@github.com