dbcve.org
SuitecrmApplication · Salesagility

CVE-2019-13335

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-02
Fix available
A fix is available. Upgrade to 7.10.19 / 7.11.7 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
SalesAgility SuiteCRM 7.10.x 7.10.19 and 7.11.x before and 7.11.7 has SSRF.

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 · moderate confidence

SalesAgility SuiteCRM versions 7.10.x before 7.10.19 and 7.11.x before 7.11.7 contain a Server-Side Request Forgery (SSRF) vulnerability. This allows an attacker to make the application server perform arbitrary requests on their behalf, potentially accessing internal services, cloud metadata endpoints, or internal network resources.

MitigationUpdate SuiteCRM to version 7.10.19 or later, or 7.11.7 or later. Additionally, implement URL allowlist validation on any endpoints that accept user-supplied URLs to prevent SSRF attacks.

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.10.0, < 7.10.19>= 7.11.0, < 7.11.7

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 navigating to Admin > About SuiteCRM in the web interface, or by examining the version.php file in the SuiteCRM root directory (usually at include/SuiteCRM/SuiteCRMVersion.php or similar).
    Affected if The installed version is 7.10.0 through 7.10.18, or 7.11.0 through 7.11.6
  2. Identify endpoints that accept user-supplied URLs
    Review the SuiteCRM codebase for endpoints or functions that accept URL parameters and perform HTTP requests. Search for functions like file_get_contents, curl_exec, or similar HTTP client functions that process user input as URLs.
    Affected if Any endpoint accepting user-supplied URLs without strict allowlist validation exists in the application
  3. Check accessibility of URL-processing functionality
    Determine if the identified URL-processing endpoints are accessible to unauthenticated users, authenticated users, or only administrators. Test by attempting to access the endpoints with minimal privileges.
    Affected if The URL-processing endpoints are accessible to users with limited privileges (non-admin users) or unauthenticated users
  4. Review application logs for suspicious outbound requests
    Examine SuiteCRM logs (located in SuiteCRM.log or in the logs directory) for any unusual outbound HTTP requests, particularly to internal IP addresses, cloud metadata endpoints (such as 169.254.169.254), or internal network resources.
    Affected if Logs show outbound requests to internal addresses, loopback addresses, or cloud metadata services that were not initiated by legitimate administrative actions

A user is affected if their SuiteCRM installation version falls within 7.10.0-7.10.18 or 7.11.0-7.11.6 and the application contains URL-accepting endpoints accessible to attackers.

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.10.19 / 7.11.7 or later
Fixed in 7.10.197.11.7
Interim mitigation

Update SuiteCRM to version 7.10.19 or later, or 7.11.7 or later. Additionally, implement URL allowlist validation on any endpoints that accept user-supplied URLs to prevent SSRF attacks.

Recommended fix High confidence

Upgrade to SuiteCRM 7.10.19 or 7.11.7 (7.11.7 recommended for latest fixes)

  1. Create a complete backup of the SuiteCRM database and file system
  2. Place the application in maintenance mode or take it offline
  3. Download SuiteCRM version 7.10.19 or 7.11.7 from the official source (docs.suitecrm.com)
  4. Extract the new version files
  5. Replace the existing SuiteCRM files with the new version files, preserving custom configurations in config.php and any custom modules in the custom/ directory
  6. Run database migrations if required (access /index.php?module=Administration&action=UpgradeWizard or use command-line upgrade tools)
  7. Clear all cached files (cache/ directory)
  8. Verify the installation by logging in and checking the About section shows the correct version
Caveat Review customizations and third-party modules for compatibility with the target version before upgrading in production

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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