dbcve.org
AgiloftApplication · Atlassian

CVE-2025-35115

HIGH · 8.1 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 30 or later.
See remediation →
90/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
Agiloft Release 28 downloads critical system packages over an insecure HTTP connection. An attacker in a Man-In-the-Middle position could replace or modify the contents of the download URL. Users should upgrade to Agiloft Release 30.

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

Agiloft Release 28 downloads critical system packages over insecure HTTP connections, allowing a Man-In-The-Middle attacker to intercept and modify the downloaded package contents. This could result in arbitrary code execution if malicious packages are substituted for legitimate ones.

MitigationUpgrade to Agiloft Release 30 or later, which uses secure HTTPS connections for downloading system packages.

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
AgiloftApplication
Affected:>= 19, < 30

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify installed Agiloft version
    Access the Agiloft admin interface and navigate to Help > About, or run 'grep -r "release" <installation_directory>/' to locate the version file. The version is typically displayed as 'Release X' where X is a number.
    Affected if The installed version is greater than or equal to 19 AND less than 30 (for example, Release 19, 24, 28, or 29). Versions below 19 or 30 and above are not affected.
  2. Confirm the system can reach external download sources
    Check if the Agiloft server has outbound network access and can resolve external hostnames. Test with: 'nslookup update.agiloft.com' or 'curl -I http://update.agiloft.com' (note: use curl with -k to ignore certificate warnings for testing purposes only).
    Affected if The server has active network connectivity to external hosts from which Agiloft downloads packages.
  3. Determine if system package downloads are enabled
    In the Agiloft admin console, navigate to System Administration > Knowledge Base Settings > Update Settings, or check configuration files in the <installation_directory>/conf/ directory for update-related parameters.
    Affected if Automatic or manual package download functionality is enabled or configured in the installation.

If your installed Agiloft version falls between Release 19 and Release 29 (inclusive) and the system has network access with package download capabilities enabled, you are affected by this vulnerability.

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 30 or later
Fixed in 30
Interim mitigation

Upgrade to Agiloft Release 30 or later, which uses secure HTTPS connections for downloading system packages.

Recommended fix High confidence

Agiloft Release 30

  1. Backup your current Agiloft database and configuration files before beginning the upgrade process
  2. Review Agiloft Release 30 release notes and upgrade documentation on wiki.agiloft.com for any migration requirements
  3. Ensure the target environment meets the system requirements for Release 30
  4. Execute the upgrade to Agiloft Release 30 following the standard upgrade procedure
  5. Verify that the upgrade completed successfully and all services are running properly
  6. Confirm that package downloads now occur over secure HTTPS connections

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

Fix this in Agiloft Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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