CVE-2019-14752
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 and 7.11.x before 7.10.20 and 7.11.8 has XSS.
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 confidenceCross-Site Scripting (XSS) vulnerability in SuiteCRM versions 7.10.x and 7.11.x before 7.10.20 and 7.11.8 allows attackers to inject malicious scripts through unvalidated input fields that are reflected in web pages without proper output encoding.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SuiteCRM versionAccess the About section in SuiteCRM (usually at Admin > About) or check the version.php file in the SuiteCRM root directoryAffected if Installed version is 7.10.0 through 7.10.19, or 7.11.0 through 7.11.7 (versions below 7.10.20 and 7.11.8)
-
Confirm SuiteCRM edition and installation pathVerify you are running a Salesagility SuiteCRM installation and note the document root path for further checksAffected if Running any SuiteCRM installation within the affected version ranges
-
Identify user input handlersReview modules that accept user-submitted data through web forms, search fields, or URL parameters - typical locations include the Search module, Quick Create forms, and parameter-driven URLsAffected if Input fields in these modules reflect user input back into HTML pages without visible output encoding
-
Test for reflected XSS parametersUse browser developer tools or a proxy to inspect HTTP responses when submitting special characters (< > " ') in form fields and query parametersAffected if Submitted characters appear unescaped in the HTTP response (e.g., <script> tags render as literal text rather than being encoded to <script>)
You are affected if your SuiteCRM version is 7.10.0-7.10.19 or 7.11.0-7.11.7 AND user input fields in your installation reflect unencoded output in web pages.
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 receive the patch for this XSS vulnerability. Alternatively, implement output encoding and input validation on affected endpoints as a compensating control.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14752 — 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-14752 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