dbcve.org
SuitecrmApplication · Salesagility

CVE-2024-50333

HIGH · 8.8 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 7.14.6 / 8.7.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. User input is not validated and is written to the filesystem. The ParserLabel::addLabels() function can be used to write attacker-controlled data into the custom language file that will be included at the runtime. This issue has been addressed in versions 7.14.6 and 8.7.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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 confidence

This is an arbitrary file write vulnerability in SuiteCRM's ParserLabel::addLabels() function. User input is not validated before being written to custom language files that are dynamically included at runtime, potentially allowing authenticated attackers to achieve remote code execution by writing malicious PHP code to the filesystem.

MitigationUpgrade to SuiteCRM version 7.14.6 or 8.7.1 or later. No workarounds are available.

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
SuitecrmApplication
Affected:< 7.14.6>= 8.0.0, < 8.7.1

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine SuiteCRM installation version
    Check the version file at /SuiteCRM/include/utils.php (search for 'suitecrm_version') or access the Admin > About section in the SuiteCRM interface
    Affected if The version number is below 7.14.6 or between 8.0.0 and 8.7.1 inclusive
  2. Verify the ParserLabel component is present
    Confirm the file SuiteCRM/include/Module/Parser/Label.php exists on the filesystem
    Affected if The file exists (the vulnerable function is present in all standard installations)
  3. Confirm authenticated access to label management
    Log into SuiteCRM and verify access to Admin > Developer Tools > Labels, or check if any user account with label editing permissions exists
    Affected if Authenticated users with label editing capabilities exist in the system
  4. Check language file directory writability
    Inspect the custom language directory (typically /custom/include/language/ or the directory referenced by $mod_strings in your installation) for write permissions
    Affected if The language directory is writable by the web server user

You are affected if your SuiteCRM version falls within the vulnerable ranges AND the language directory is writable AND authenticated users have access to label editing functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.14.6 / 8.7.1 or later
Fixed in 7.14.68.7.1
Interim mitigation

Upgrade to SuiteCRM version 7.14.6 or 8.7.1 or later. No workarounds are available.

Recommended fix High confidence

SuiteCRM 7.14.6 (for 7.x line) or SuiteCRM 8.7.1 (for 8.x line)

  1. 1. Back up your current SuiteCRM installation and database before upgrading.
  2. 2. For SuiteCRM 7.x line: Download version 7.14.6 from the official SuiteCRM repository (github.com/salesagility/SuiteCRM).
  3. 3. For SuiteCRM 8.x line: Download version 8.7.1 from the official SuiteCRM repository (github.com/salesagility/SuiteCRM).
  4. 4. Replace the existing SuiteCRM files with the new version files, preserving your config.php and any custom configurations.
  5. 5. Clear the cache directory (cache/ folder) to ensure old files are not loaded.
  6. 6. Verify the upgrade by logging in and testing core CRM functionality.
Caveat Standard upgrade risks apply - always test in staging environment first; review release notes for any configuration or feature changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Suitecrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50333 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50333 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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