Live › vulnerability › CVE-2026-42269
Go to dashboardCountly's data-migration deletion route passes a user-supplied export ID into a recursive delete without path validation. An authenticated administrator or user with migration permission can delete writable files or directory trees on the server, causing data loss or service disruption.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Self-hosted Countly servers running a version before 24.05.50 or 25.03.44 where the data_migration plugin is present and users hold application administrator or migration permission. Attackers need an authenticated account with those rights, so instances limited to trusted admins carry less risk. Managed Countly hosting is handled by the vendor.
No product ranges from the sources yet.
24.05.50 and 25.03.44 are affectedplugins/data_migration24.05.50 or 25.03.44 (or later in the same branch)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
countly-server is the server-side part of Countly, a product analytics solution. Prior to 24.05.50 and 25.03.44, the authenticated data-migration deletion route in plugins/data_migration/api/api.js passes the user-controlled exportid to clean_up_data without path validation. plugins/data_migration/api/data_migration_helper.js concatenates that identifier into a path resolved outside the intended import directory and calls remove recursively, allowing an application administrator or user with migration permission to delete writable files or directory trees and cause data loss or service disruption. This issue is fixed in versions 24.05.50 and 25.03.44.
This page as .md · .json · in your agent: get_signal("CVE-2026-42269")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.