dbcve.org
OpenatlasApplication · Craws

CVE-2025-60915

HIGH · 8.1 CVSS v3.1 Published 2025-11-24
Fix available
A fix is available. Upgrade to after 8.12.0 or later.
See remediation →
87/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
An issue in the size query parameter (/views/file.py) of Austrian Archaeological Institute Openatlas before v8.12.0 allows attackers to execute a path traversal via a crafted request.

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 · moderate confidence

A path traversal vulnerability exists in the size query parameter of /views/file.py in Openatlas before v8.12.0, allowing attackers to access files outside the intended directory through crafted requests with traversal sequences.

MitigationUpgrade to Openatlas v8.12.0 or later. Implement strict input validation on the size parameter to reject path traversal sequences (../) and restrict file access to allowed directories.

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
OpenatlasApplication
Affected:<= 8.12.0

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Openatlas installation and version
    Locate the Openatlas application and check its version number. Common locations include the installation directory, package manager, or the application itself (often displayed in UI footer or admin panel). Compare the installed version to the affected range: versions <= 8.12.0
    Affected if Openatlas is installed and the version is 8.12.0 or lower
  2. Confirm the vulnerable endpoint exists
    Locate the file views/file.py in the Openatlas installation directory. Verify that this endpoint is accessible within the application routing. Check the application routes or URL structure to confirm /views/file.py is reachable
    Affected if The file views/file.py exists and is accessible via HTTP/HTTPS
  3. Verify size parameter is accepted
    Review the views/file.py source code to confirm it accepts a 'size' query parameter. Check the parameter handling logic to see if it processes the size value for file operations
    Affected if The endpoint accepts and processes a 'size' query parameter without validation
  4. Check for path traversal protections
    Inspect the source code of views/file.py to see if input validation exists on the size parameter. Look for filtering or sanitization of '../' sequences or other path traversal patterns
    Affected if No input validation or path traversal protection is implemented on the size parameter

A user is affected if Openatlas version 8.12.0 or lower is installed with the views/file.py endpoint accessible and the size parameter accepting unvalidated input.

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 a release after 8.12.0
Interim mitigation

Upgrade to Openatlas v8.12.0 or later. Implement strict input validation on the size parameter to reject path traversal sequences (../) and restrict file access to allowed directories.

Recommended fix High confidence

8.12.0

  1. 1. Backup the existing Openatlas database and all application files
  2. 2. Review the official Openatlas release notes for version 8.12.0 to understand changes and any specific upgrade requirements
  3. 3. Download Openatlas version 8.12.0 or the latest stable release from the official repository
  4. 4. Follow the standard Openatlas upgrade procedure documented in the project's installation/upgrade guide
  5. 5. Verify the installation by checking that the application runs without errors
  6. 6. Test that the /views/file.py endpoint now properly sanitizes the size parameter and blocks path traversal attempts
  7. 7. Confirm normal file handling functionality still works as expected

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

Fix this in Openatlas 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-60915 — 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-60915 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