dbcve.org
SuitecrmApplication · Salesagility

CVE-2022-50589

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 7.12.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 versions prior to 7.12.6 contain a SQL injection vulnerability within the processing of the ‘uid’ parameter within the ‘export’ functionality. Successful exploitation allows remote unauthenticated attackers to ultimately execute arbitrary code.

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

SQL injection vulnerability in SuiteCRM's export functionality where the 'uid' parameter is not properly sanitized, allowing remote unauthenticated attackers to inject malicious SQL queries that can lead to arbitrary code execution.

MitigationUpgrade to SuiteCRM version 7.12.6 or later which contains the patch for this vulnerability.

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.12.6

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
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 checks

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

  1. Determine installed SuiteCRM version
    Check the SuiteCRM version by visiting the admin panel (usually at /index.php?module=Administration&action=UpgradeWizard) or by locating the version in the file /suitecrm_version.php or in the suitecrm.log file during startup.
    Affected if The installed version is below 7.12.6 (for example, 7.12.5, 7.12.4, 7.11.x, etc.)
  2. Verify export functionality is network-accessible
    Confirm that the SuiteCRM export endpoint (typically /index.php?module=<any>&action=export) is accessible from the network without authentication. This can be tested by attempting a request to the export action without logging in.
    Affected if The export functionality is exposed to unauthenticated network access (no IP restrictions, firewall rules, or authentication requirements blocking it)
  3. Identify if the uid parameter is processed in export
    Locate and inspect the export action handler in the SuiteCRM codebase, specifically looking for code that processes the 'uid' parameter. Search in modules/<any>/export.php or similar export handling files.
    Affected if The export functionality processes a 'uid' parameter without proper input sanitization or parameterized queries
  4. Check for SQL injection vulnerability indicators
    Review server logs (Apache/nginx error logs, PHP logs, SuiteCRM logs) for unusual SQL syntax errors, especially those containing SQL commands or unexpected characters in requests to export functionality with the uid parameter.
    Affected if Unusual SQL error messages appear in logs related to export requests, or abnormal database query patterns are observed from the export endpoint

You are affected if your SuiteCRM installation is version 7.12.5 or earlier AND the export functionality is accessible without authentication, allowing an attacker to inject SQL through the uid parameter.

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.12.6 or later
Fixed in 7.12.6
Interim mitigation

Upgrade to SuiteCRM version 7.12.6 or later which contains the patch for this vulnerability.

Recommended fix High confidence

SuiteCRM 7.12.6 or latest stable 7.x release

  1. Create a complete backup of the SuiteCRM database and file system before proceeding with any changes
  2. Download SuiteCRM version 7.12.6 or the latest stable release from the official SuiteCRM repository (github.com/salesagility/SuiteCRM)
  3. Test the upgrade in a non-production environment first to verify compatibility with existing customizations and integrations
  4. In a production environment, place the application in maintenance mode or ensure no users are accessing the system during the upgrade
  5. Extract and deploy the new SuiteCRM files, preserving the config.php and any custom configuration files
  6. Run the database upgrade script if provided (typically via Admin > Upgrade Wizard in the UI or command line), or allow SuiteCRM to automatically perform schema migrations on first access
  7. Verify that the export functionality with the 'uid' parameter no longer accepts arbitrary SQL payloads
  8. After upgrade, clear all caches (Admin > Cache Management) and rebuild relationships if needed
Caveat Review custom modules and integrations for compatibility with 7.12.x before production deployment; standard SuiteCRM upgrade precautions apply

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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