dbcve.org
AllegraApplication · Alltena

CVE-2025-3485

HIGH · 8.8 CVSS v3.1 Published 2025-06-06
Fix available
A fix is available. Upgrade to 8.1.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Allegra extractFileFromZip Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Allegra. Authentication is required to exploit this vulnerability. The specific flaw exists within the implementation of the extractFileFromZip method. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26524.

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 vulnerability is a directory traversal flaw in the extractFileFromZip method of Allegra software, where user-supplied file paths are not validated before file operations. An authenticated attacker can craft a ZIP file containing paths with directory traversal sequences (e.g., ../../../) to write files to arbitrary locations on the system and achieve RCE.

MitigationImplement strict path validation in the extractFileFromZip method to verify that extracted paths remain within the intended target directory. Use canonical path comparisons and reject any path containing traversal sequences or absolute paths.

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
AllegraApplication
Affected:< 8.1.2

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Allegra version
    Check the software's about page, version info in the application header, or query the Allegra API/CLI for version metadata. Common locations: Help > About, or inspect the allegra-version file in the installation directory.
    Affected if The version is lower than 8.1.2 (e.g., 8.0.x, 7.x, or any version string without 8.1.2 or higher).
  2. Verify authentication status
    Determine whether your Allegra instance requires authentication for access. Check if user accounts are enabled and you have valid login credentials.
    Affected if You can authenticate to the Allegra application (valid user credentials exist and login is successful).
  3. Confirm ZIP file import feature is accessible
    Check if the file import/upload functionality that processes ZIP archives is available in your user role. Look for features like bulk import, file upload, or attachment import in the UI or API endpoints.
    Affected if The authenticated user role permits access to ZIP file upload or import functionality.
  4. Inspect file write permissions on server
    Review file system permissions on the Allegra installation directory and its subdirectories. Check if the application user has write access to directories outside the intended upload workspace.
    Affected if The Allegra service account has write permissions to directories outside the designated extraction target folder.

You are affected if your Allegra version is below 8.1.2, you have authenticated access to the application, and the ZIP file import feature is enabled for your user account.

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

Implement strict path validation in the extractFileFromZip method to verify that extracted paths remain within the intended target directory. Use canonical path comparisons and reject any path containing traversal sequences or absolute paths.

Recommended fix High confidence

Allegra 8.1.2 or later

  1. 1. Back up your current Allegra installation and database
  2. 2. Verify your current Allegra version is below 8.1.2
  3. 3. Download Allegra version 8.1.2 or later from the official vendor source
  4. 4. Follow the vendor's standard upgrade procedure for your deployment method
  5. 5. After upgrade, verify the extractFileFromZip method properly validates paths and does not accept directory traversal sequences (e.g., ../)
  6. 6. Test that file extraction from ZIP archives functions correctly with normal file paths
Caveat Review vendor release notes for any breaking changes between your current version and 8.1.2; test in non-production environment first

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

Fix this in Allegra Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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