CVE-2019-16922
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 7.10.x before 7.10.20 and 7.11.x before 7.11.8 allows unintended public exposure of files.
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 confidenceSuiteCRM versions 7.10.x before 7.10.20 and 7.11.x before 7.11.8 contain a vulnerability that allows unintended public exposure of files, likely through improper access controls or path handling in the application.
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.10.0, < 7.10.20>= 7.11.0, < 7.11.8CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Locate SuiteCRM version fileFind the version.php file in the SuiteCRM installation directory (typically includes/version.php or cache/include/modules/<module>/version.php). Open it and read the $sugar_config['sugar_version'] value or similar version constant.Affected if The version number is 7.10.x where x is less than 20, or 7.11.x where x is less than 8
-
Check version via admin interfaceLog into the SuiteCRM admin panel and navigate to Admin > About SuiteCRM to view the installed version number.Affected if The displayed version falls within the ranges 7.10.0 to 7.10.19, or 7.11.0 to 7.11.7
-
Verify application network exposureDetermine if the SuiteCRM instance is accessible from untrusted networks or the public internet by checking web server configuration and firewall rules.Affected if The application is exposed to the internet or untrusted users AND the version is within the affected ranges listed above
-
Inspect access control configurationReview the SuiteCRM .htaccess file (if Apache) or web server configuration for any rules that may permit directory listing or direct file access to sensitive paths.Affected if Permissive access rules exist AND the version is vulnerable as determined in step 1 or 2
You are affected if your SuiteCRM version is 7.10.0 through 7.10.19, or 7.11.0 through 7.11.7, and the application is accessible to untrusted users.
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.
From vendor data7.10.207.11.8
Upgrade SuiteCRM to version 7.10.20, 7.11.8, or later to resolve the file exposure vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16922 — 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-2019-16922 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