AgiloftApplication · Atlassian
CVE-2025-35114
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 · uneditedAgiloft Release 28 contains several accounts with default credentials that could allow local privilege escalation. The password hash is known for at least one of the accounts and the credentials could be cracked offline. 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 confidenceAgiloft Release 28 ships with multiple built-in accounts using default credentials. At least one account's password hash is publicly known and can be cracked offline using standard password cracking tools, enabling local privilege escalation to gain elevated access.
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
>= 19, < 30CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Identify installed Agiloft versionLocate the installed Agiloft version number in the system (check administration panel, about page, or version file in the installation directory)Affected if The version is greater than or equal to 19 and less than 30
-
Locate built-in or default accountsQuery the user/account management system for accounts that are shipped with the product by default, typically found in the user administration module or configuration filesAffected if Default built-in accounts exist and remain enabled with factory-set credentials
-
Verify default credentials have been changedAttempt to authenticate using known default username/password combinations for the built-in accounts, or check password hash storage for evidence of unchanged default valuesAffected if Any built-in account still uses its original default password or the corresponding hash matches publicly known values
-
Check for privilege escalation exposureExamine whether the built-in accounts grant elevated or administrative privileges within the applicationAffected if Built-in accounts with default credentials provide access to privileged functions or administrative roles
The environment is affected if the installed Agiloft version is between 19 and 29 inclusive AND any built-in default accounts remain configured with unchanged default credentials.
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 · scoped30
Upgrade to Agiloft Release 30 which removes or changes the default credentials. Prior to upgrade, ensure backups are tested and plan for functionality validation in a staging environment.
Agiloft Release 30
- Plan and schedule maintenance window for the Agiloft upgrade
- Review Agiloft Release 30 release notes and migration guide for any pre-upgrade requirements
- Perform a full backup of the current Agiloft database and configuration
- Upgrade Agiloft from current version (19-28) to Release 30
- After upgrade, identify all system accounts and change default passwords immediately
- Verify that all default credentials have been replaced with strong, unique passwords
- Review user accounts and ensure no default or weak credentials remain in use
- Test that all functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Agiloft
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35114 — 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-2025-35114 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