dbcve.org
SuitecrmApplication · Salesagility

CVE-2024-50335

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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. The "Publish Key" field in SuiteCRM's Edit Profile page is vulnerable to Reflected Cross-Site Scripting (XSS), allowing an attacker to inject malicious JavaScript code. This can be exploited to steal CSRF tokens and perform unauthorized actions, such as creating new administrative users without proper authentication. The vulnerability arises due to insufficient input validation and sanitization of the Publish Key field within the SuiteCRM application. When an attacker injects a malicious script, it gets executed within the context of an authenticated user's session. The injected script (o.js) then leverages the captured CSRF token to forge requests that create new administrative users, effectively compromising the integrity and security of the CRM instance. 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

SuiteCRM contains a reflected XSS vulnerability in the 'Publish Key' field of the Edit Profile page. An attacker can inject malicious JavaScript that executes in authenticated users' sessions, allowing theft of CSRF tokens and forging of requests to create unauthorized administrative users. The vulnerability affects versions prior to 7.14.6 and 8.7.1.

MitigationUpgrade SuiteCRM to version 7.14.6, 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Identify SuiteCRM version
    Check the version file in the SuiteCRM root directory (usually VERSION file or similar), or access the Admin panel > System Information to view the installed version number
    Affected if The installed version is below 7.14.6 or between 8.0.0 and 8.7.1 (exclusive)
  2. Confirm Edit Profile page exists
    Navigate to the Edit Profile page in the SuiteCRM interface (usually at /index.php?module=Users&action=EditView or similar), verify the page loads and contains input fields
    Affected if The Edit Profile page is accessible to authenticated users in the environment
  3. Locate the Publish Key field
    On the Edit Profile page, identify the 'Publish Key' input field (this is a profile field that may be present depending on configuration)
    Affected if The 'Publish Key' field is present and can accept user input
  4. Verify authenticated access exists
    Confirm that regular authenticated users (non-admin) can access and modify their own profile settings
    Affected if Non-administrative users can access profile edit functionality

A user is affected if their SuiteCRM installation runs version 7.x below 7.14.6 or version 8.x below 8.7.1 and authenticated users can access the Edit Profile page with the Publish Key field.

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 SuiteCRM to version 7.14.6, 8.7.1, or later. No workarounds are available.

Recommended fix High confidence

7.14.6 for 7.x branch; 8.7.1 for 8.x branch

  1. 1. Backup your SuiteCRM database and application files before upgrading
  2. 2. If running SuiteCRM 7.x version (< 7.14.6), upgrade to version 7.14.6
  3. 3. If running SuiteCRM 8.x version (>= 8.0.0, < 8.7.1), upgrade to version 8.7.1
  4. 4. Clear application cache after upgrade (delete cache/ directory contents)
  5. 5. Verify the upgrade was successful by logging in and checking the SuiteCRM version
  6. 6. Confirm the Edit Profile page 'Publish Key' field now properly sanitizes input
Caveat Standard CRM upgrade precautions apply - test in staging environment first, especially if custom modules or third-party add-ons are installed

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50335 — 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-50335 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