Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-69601: n/a

0
Medium
VulnerabilityCVE-2025-69601cvecve-2025-69601
Published: Wed Jan 28 2026 (01/28/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

A directory traversal (Zip Slip) vulnerability exists in the “Static Sites” feature of 66biolinks v44.0.0 by AltumCode. Uploaded ZIP archives are automatically extracted without validating or sanitizing file paths. An attacker can include traversal sequences (e.g., ../) in ZIP entries to write files outside the intended extraction directory. This allows static files (html, js, css, images) file write to unintended locations, or overwriting existing HTML files, potentially leading to content defacement and, in certain deployments, further impact if sensitive files are overwritten.

AI-Powered Analysis

AILast updated: 02/05/2026, 08:30:39 UTC

Technical Analysis

CVE-2025-69601 is a directory traversal vulnerability classified under CWE-22, affecting the Static Sites feature of 66biolinks version 44.0.0 developed by AltumCode. The vulnerability arises because the application automatically extracts uploaded ZIP archives without validating or sanitizing the file paths contained within the archive entries. An attacker can craft ZIP files with entries containing directory traversal sequences such as '../' to escape the intended extraction directory. This allows arbitrary file writes to locations outside the designated static site folder. The impact includes overwriting existing static files like HTML, JavaScript, CSS, or image files, which can lead to website defacement or manipulation of site content. In some deployment scenarios, if the extraction path overlaps with sensitive configuration or data files, the attacker could overwrite these, potentially escalating the impact beyond content defacement. The vulnerability requires the attacker to have authenticated access to upload ZIP files but does not require further user interaction. The CVSS 3.1 base score is 6.5, reflecting a medium severity with network attack vector, low attack complexity, and no user interaction required. No patches or known exploits are currently reported, but the vulnerability is publicly disclosed and should be addressed promptly to prevent exploitation.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to those using 66biolinks v44.0.0 for managing static websites or landing pages. Successful exploitation can lead to unauthorized modification of website content, resulting in reputational damage, loss of customer trust, and potential misinformation dissemination. In cases where the extraction directory overlaps with sensitive files, there could be further risks such as configuration corruption or exposure of sensitive data, which may lead to compliance violations under GDPR if personal data is affected. The ability to overwrite static assets could also be leveraged to inject malicious scripts, potentially facilitating client-side attacks like cross-site scripting (XSS). Given the medium severity and the requirement for authenticated access, the threat is moderate but significant for organizations relying on this software for public-facing web content. The absence of known exploits suggests a window for proactive mitigation before active attacks emerge.

Mitigation Recommendations

European organizations should immediately audit their use of 66biolinks, specifically version 44.0.0, and restrict access to the Static Sites upload feature to trusted users only. Implement strict input validation and sanitization on ZIP file entries to prevent directory traversal sequences from being processed. If possible, disable automatic extraction of ZIP files or switch to manual extraction with path validation. Monitor file system changes in the static site directories for unexpected modifications. Employ web application firewalls (WAFs) to detect and block suspicious upload patterns. Regularly back up static site content to enable quick restoration in case of defacement. Engage with AltumCode or the software vendor for official patches or updates addressing this vulnerability. Additionally, consider isolating the extraction environment using containerization or sandboxing to limit the impact of potential exploitation. Finally, enforce strong authentication and access controls to minimize the risk of unauthorized uploads.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-01-09T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 697a5e9e4623b1157ce6c331

Added to database: 1/28/2026, 7:08:14 PM

Last enriched: 2/5/2026, 8:30:39 AM

Last updated: 2/7/2026, 5:00:57 AM

Views: 31

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats