CVE-2024-32641
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMasa CMS is an open source Enterprise Content Management platform. Masa CMS versions prior to 7.2.8, 7.3.13, and 7.4.6 are vulnerable to remote code execution. The vulnerability exists in the addParam function, which accepts user input via the criteria parameter. This input is subsequently evaluated by setDynamicContent, allowing an unauthenticated attacker to execute arbitrary code via the m tag. The vulnerability is patched in versions 7.2.8, 7.3.13, and 7.4.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMasa CMS versions prior to 7.2.8, 7.3.13, and 7.4.6 contain an unauthenticated remote code execution vulnerability in the addParam function. The criteria parameter accepts user input that is subsequently evaluated by setDynamicContent, allowing arbitrary code execution via the m tag.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.2.8>= 7.3, < 7.3.13>= 7.4.0, < 7.4.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Masa CMS versionLocate the version file or admin panel that displays the Masa CMS version numberAffected if version is less than 7.2.8, or between 7.3.0 and 7.3.12, or between 7.4.0 and 7.4.5
-
Confirm addParam function is accessibleCheck if the /addParam endpoint or function is reachable via HTTP request without authenticationAffected if the endpoint responds and accepts parameters without requiring authentication
-
Verify criteria parameter processingTest if the criteria parameter is processed by setDynamicContent by sending a request with m tag syntax to the addParam functionAffected if the server evaluates m tag expressions passed through the criteria parameter
A system is affected if it runs any Masa CMS version below 7.2.8, between 7.3.0-7.3.12, or between 7.4.0-7.4.5 AND has the addParam function with criteria parameter accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.2.87.3.137.4.6
Upgrade to Masa CMS version 7.2.8, 7.3.13, or 7.4.6 to remediate this vulnerability.
Upgrade to MasaCMS 7.2.8, 7.3.13, or 7.4.6 depending on your current version branch
- 1. Identify the currently installed MasaCMS version by checking the admin dashboard or version file
- 2. Create a complete backup of the MasaCMS installation including database and all files
- 3. Based on your current version branch, upgrade to the corresponding fixed release: If currently on 7.2.x, upgrade to 7.2.8; If currently on 7.3.x, upgrade to 7.3.13; If currently on 7.4.x, upgrade to 7.4.6
- 4. Download the appropriate version from the official MasaCMS releases (github.com/MasaCMS/MasaCMS/releases)
- 5. Follow the standard MasaCMS upgrade documentation to apply the update
- 6. Verify the upgrade was successful by checking the version in the admin interface
- 7. Test that the m tag functionality works correctly with the patched addParam function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32641 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data