dbcve.org
CWE-377Weakness · CWE-377

CVE-2025-67223

HIGH · 7.5 CVSS v3.1 Published 2026-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The Aranda File Server (AFS) component in Aranda Software Aranda Service Desk before 8.3.12 stores daily activity logs with predictable names in a publicly accessible directory, which allows unauthenticated remote attackers to obtain direct virtual paths of uploaded files and bypass access controls to download sensitive documents containing PII.

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 Aranda File Server (AFS) component in Aranda Service Desk versions before 8.3.12 stores daily activity logs with predictable, sequential filenames in a directory exposed via the web server. Attackers can enumerate these log files to discover virtual paths of uploaded documents and directly download sensitive files containing PII, bypassing all application-level access controls.

MitigationUpgrade to Aranda Service Desk 8.3.12 or later, and ensure log directories are not publicly accessible via the web server while restricting filesystem permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

  1. Identify Aranda Service Desk installation and version
    Locate the Aranda Service Desk installation directory and check the version file or application metadata. Common locations include the installation root folder or application properties files that display the current version.
    Affected if The installed version is below 8.3.12
  2. Verify Aranda File Server (AFS) component is enabled
    Check the Aranda Service Desk configuration for the AFS component. This is typically found in the application configuration files, service settings, or administration console where file server modules are listed.
    Affected if AFS component is installed and active in the configuration
  3. Locate the AFS log directory
    Search for the daily activity log directory used by AFS. Check application configuration files or default installation paths for log storage locations used by the file server component.
    Affected if Log directory exists and contains sequentially named log files
  4. Confirm log directory is web-accessible
    Test whether the log directory or its contents are reachable via HTTP/HTTPS requests through the web server. Attempt to access the directory listing or known log file patterns via the web URL.
    Affected if The log directory or log files are accessible via the web server URL, allowing enumeration

A user is affected if running Aranda Service Desk versions before 8.3.12 with AFS enabled and the log directory exposed via the web server, allowing unauthorized access to sensitive files.

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 to Aranda Service Desk 8.3.12 or later, and ensure log directories are not publicly accessible via the web server while restricting filesystem permissions.

Recommended fix High confidence

Aranda Service Desk 8.3.12 or later

  1. 1. Identify the current version of Aranda Service Desk installation by checking the application or system information.
  2. 2. Create a complete backup of the current installation including all databases, configuration files, and uploaded documents.
  3. 3. Download Aranda Service Desk version 8.3.12 or later from the official Aranda Software vendor channels (arandasoft.com).
  4. 4. Review the official upgrade documentation for Aranda Service Desk to understand prerequisites and upgrade procedures.
  5. 5. Execute the upgrade following the vendor's recommended upgrade path, ensuring all AFS (Aranda File Server) components are updated.
  6. 6. After upgrading, verify that the log file naming convention has been changed from predictable names to non-predictable names.
  7. 7. Confirm that the publicly accessible directory no longer exposes activity logs and that access controls are properly enforced.
  8. 8. Test that legitimate users can still access uploaded files through proper authentication and authorization mechanisms.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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