CVE-2022-50590
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 · uneditedSuiteCRM versions prior to 7.12.6 contain a type confusion vulnerability within the processing of the ‘module’ parameter within the ‘deleteAttachment’ functionality. Successful exploitation allows remote unauthenticated attackers to alter database objects including changing the email address of the administrator.
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 confidenceSuiteCRM versions before 7.12.6 contain a type confusion vulnerability in the 'module' parameter processing of the 'deleteAttachment' function. This allows remote unauthenticated attackers to manipulate database objects through the vulnerability, specifically enabling modification of the administrator's email address.
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.12.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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed SuiteCRM versionLocate the version file in the SuiteCRM installation directory. Common paths include 'include/SuiteApplication.php', 'suitecrm_version.php', or check the About page in the SuiteCRM admin interface under 'Admin > About'. Compare the version number to the affected range (anything below 7.12.6).Affected if The installed version is below 7.12.6 (e.g., 7.12.0 through 7.12.5)
-
Verify deleteAttachment endpoint is accessibleCheck if the deleteAttachment function is exposed via the REST API or direct URL access. This typically involves requests to endpoints like 'index.php?module=SomeModule&action=deleteAttachment' or API calls to the Attachment API. Use web scanner or manually test a request to an attachment deletion endpoint.Affected if The deleteAttachment endpoint is reachable without authentication or with low-privilege user access
-
Inspect application logs for suspicious deleteAttachment callsReview SuiteCRM application logs (typically in 'logs/') for any unusual or unauthorized deleteAttachment function calls, especially those targeting the Users module or administrator account records. Look for parameter tampering attempts on the 'module' parameter.Affected if Log entries show deleteAttachment calls with manipulated module parameter values targeting sensitive modules
-
Check administrator account email addressQuery the users table or navigate to Admin > User Management in the SuiteCRM UI to verify the administrator account email address. Compare against known legitimate values or check for unauthorized changes.Affected if The administrator account email address has been changed to an unexpected value without legitimate admin action
A user is affected if their SuiteCRM installation is version 7.12.5 or earlier AND the deleteAttachment functionality is exposed to unauthenticated or low-privilege access, allowing potential modification of the administrator email address.
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.12.6
Upgrade SuiteCRM to version 7.12.6 or later to address the type confusion vulnerability in the deleteAttachment functionality.
SuiteCRM 7.12.6
- 1. Backup your SuiteCRM database and files before making any changes
- 2. Download SuiteCRM version 7.12.6 or later from the official repository (https://github.com/salesagility/SuiteCRM)
- 3. Replace the existing SuiteCRM files with the new version, preserving your custom configurations and the config.php file
- 4. Clear the cache by deleting all contents in the cache/ directory
- 5. Run a quick repair and rebuild via Admin > Repair > Quick Repair and Rebuild
- 6. Verify the deleteAttachment functionality works correctly and test that the type confusion vulnerability is mitigated
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-2022-50590 — 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-2022-50590 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