dbcve.org
AgiloftApplication · Atlassian

CVE-2025-35113

HIGH · 7.2 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 31 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 does not properly neutralize special elements used in an EUI template engine, allowing an authenticated attacker to achieve remote code execution by loading a specially crafted payload. Users should upgrade to Agiloft Release 31.

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 contains a server-side template injection vulnerability in its EUI (Extended User Interface) template engine. The template engine fails to properly sanitize special elements, allowing an authenticated attacker to inject malicious template code that executes operating system commands on the host server.

MitigationUpgrade Agiloft to Release 31 or later, which contains the patched template engine. As this is an authenticated RCE vulnerability, also review user accounts and audit access logs for indicators of compromise.

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, < 31

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Agiloft installation
    Locate Agiloft installation directory or check for Agiloft service/process running on the server. Common paths include /opt/agiloft or C:\Program Files\Agiloft on Windows systems.
    Affected if Agiloft software is present on the system
  2. Identify installed Agiloft version
    Check the version number of the installed Agiloft instance. Version information is typically accessible through the Agiloft admin interface under System Administration > System Setup, or by examining version files in the installation directory.
    Affected if Installed version is >= 19 and < 31
  3. Verify EUI is enabled
    Check whether the Extended User Interface (EUI) feature is enabled in the Agiloft configuration. This is typically configured in the system settings or can be verified by attempting to access EUI endpoints.
    Affected if EUI feature is enabled and accessible to authenticated users
  4. Confirm authenticated access exists
    Review user accounts and authentication configuration to determine if any user accounts exist that could provide authenticated access to the system.
    Affected if Any valid user accounts are configured in the system

The environment is affected if Agiloft is installed with a version between 19 and 31 (exclusive of 31) and the EUI feature is enabled, allowing authenticated users to access the template engine.

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

Upgrade Agiloft to Release 31 or later, which contains the patched template engine. As this is an authenticated RCE vulnerability, also review user accounts and audit access logs for indicators of compromise.

Recommended fix High confidence

Agiloft Release 31

  1. Download Agiloft Release 31 from the official Agiloft distribution channels
  2. Review the Agiloft Release 31 upgrade documentation for version-specific migration requirements
  3. Create a complete backup of the current Agiloft installation including database and configuration files
  4. Execute the upgrade process following the documented upgrade path for your current version
  5. Verify the upgrade was successful by checking the version number in the system
  6. Test critical business workflows to ensure the EUI template engine functions correctly after upgrade
Caveat Upgrading across many major releases (from 19-30 to 31) may require careful migration testing; review release notes for breaking changes between your current version and Release 31

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

Fix this in Agiloft Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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