CVE-2021-45898
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 before 7.12.3 and 8.x before 8.0.2 allows local file inclusion.
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 confidenceThis is a local file inclusion (LFI) vulnerability in SuiteCRM affecting versions before 7.12.3 and 8.x before 8.0.2. The flaw allows attackers to manipulate input parameters to include arbitrary files from the server's filesystem, potentially exposing sensitive configuration files, credentials, or system files.
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.3>= 8.0.0, < 8.0.2= 8.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SuiteCRM versionLocate the version file or entry point in your SuiteCRM installation (commonly found in version.php or include/utils.php in the SuiteCRM root directory) and read the version numberAffected if the installed version is less than 7.12.3, or is 8.0.0, 8.0.1, or 8.0.2 (the 8.x branch below 8.0.2)
-
Verify web server exposureConfirm that the SuiteCRM web directory is accessible via HTTP/HTTPS from untrusted networksAffected if the web interface is publicly accessible without network-level restrictions
-
Review access logs for LFI patternsExamine web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests containing ../, ..\, or absolute paths in query parameters related to file inclusion pointsAffected if unusual file path traversal patterns appear in logs, especially targeting system files like /etc/passwd or configuration directories
You are affected if your SuiteCRM version falls below 7.12.3 in the 7.x branch or is any 8.0.x version before 8.0.2, and the application is reachable over a network where attackers can manipulate input parameters.
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.38.0.2
Upgrade SuiteCRM to version 7.12.3 or later, or 8.0.2 or later. Until patched, restrict web server access and monitor for suspicious file access patterns.
SuiteCRM 7.12.3 or 8.0.2 (depending on your current major version)
- 1. Back up your SuiteCRM database and files
- 2. Download SuiteCRM 7.12.3 (for 7.x line) or SuiteCRM 8.0.2 (for 8.x line) from the official repository
- 3. Review the official upgrade guide at docs.suitecrm.com for your specific version path
- 4. Test the upgrade in a staging environment before production deployment
- 5. Execute the upgrade following standard SuiteCRM upgrade procedures
- 6. Verify the installation by logging in and testing core functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45898 — 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-2021-45898 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