dbcve.org
SuitecrmApplication · Salesagility

CVE-2025-54786

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. In versions 7.14.6 and 8.8.0, the broken authentication in the legacy iCal service allows unauthenticated access to meeting data. An unauthenticated actor can view any user's meeting (calendar event) data given their username, related functionality allows user enumeration. This is fixed in versions 7.14.7 and 8.8.1.

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 confidence

The legacy iCal service in SuiteCRM versions 7.14.6 and 8.8.0 contains a broken authentication flaw that permits unauthenticated attackers to access meeting and calendar event data for any user by supplying the target's username. The same vulnerable endpoint also allows user enumeration, enabling attackers to discover valid usernames before extracting calendar information.

MitigationUpgrade SuiteCRM to version 7.14.7 or 8.8.1 to patch the authentication bypass in the legacy iCal service. Additionally, restrict external access to the iCal endpoints at the network level as a defense-in-depth measure until patching is complete.

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.14.6= 8.8.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check SuiteCRM installed version
    Locate the version file or admin interface in your SuiteCRM installation. Common locations include a version.php file in the root directory or the 'About' section in the admin panel.
    Affected if The installed version is exactly 7.14.6 or exactly 8.8.0
  2. Identify legacy iCal endpoint accessibility
    Check if the legacy iCal endpoint is accessible on your server. This is typically found at a path containing 'ical' or 'vcal' in the URL structure, often under the legacy or include directories.
    Affected if The iCal endpoint is exposed and reachable without authentication
  3. Test for authentication bypass
    Attempt to access calendar data by making a request to the iCal endpoint with a known username parameter without providing valid authentication credentials.
    Affected if The request returns meeting or calendar event data for the specified user without requiring a login session
  4. Test for user enumeration
    Make unauthenticated requests to the iCal endpoint with different usernames and observe the responses for differences that indicate valid versus invalid accounts.
    Affected if The endpoint reveals whether a username exists based on different response messages or behavior
  5. Review server access logs
    Examine web server access logs for requests to iCal endpoints that include username parameters but lack corresponding authentication tokens or session cookies.
    Affected if Unauthenticated requests to iCal endpoints with username parameters appear in the logs

Your environment is affected if you are running SuiteCRM version 7.14.6 or 8.8.0 AND the legacy iCal endpoint is accessible without authentication, allowing calendar data access or user enumeration.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SuiteCRM to version 7.14.7 or 8.8.1 to patch the authentication bypass in the legacy iCal service. Additionally, restrict external access to the iCal endpoints at the network level as a defense-in-depth measure until patching is complete.

Recommended fix High confidence

7.14.6 → 7.14.7 (or 8.8.0 → 8.8.1)

  1. 1. Identify your current SuiteCRM version by checking the version.php file or the About section in the admin panel
  2. 2. Create a complete backup of your SuiteCRM database and all application files
  3. 3. Download SuiteCRM version 7.14.7 (if running 7.14.6) or version 8.8.1 (if running 8.8.0) from the official SuiteCRM downloads page at suitecrm.com or github.com
  4. 4. Extract the new version package and upload all files to your server, overwriting existing files
  5. 5. Run the upgrade wizard by accessing SuiteCRM through your web browser (e.g., navigate to your SuiteCRM URL/upgrade.php)
  6. 6. Follow the on-screen prompts to complete the database upgrade
  7. 7. Clear the cache by deleting contents of the cache/ folder (except .htaccess)
  8. 8. Verify the fix by attempting to access the iCal endpoint without authentication - it should now require authentication

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Suitecrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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