dgtlmoon Changedetection.io 0.55.7 requirements.txt excessive authentication

Summaryinfo

A vulnerability, which was classified as problematic, has been found in dgtlmoon Changedetection.io 0.55.7. This issue affects some unknown processing of the file requirements.txt. The manipulation leads to excessive authentication. This vulnerability is listed as CVE-2026-71205. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in dgtlmoon Changedetection.io 0.55.7. This issue affects an unknown functionality of the file requirements.txt. The manipulation with an unknown input leads to a excessive authentication vulnerability. Using CWE to declare the problem leads to CWE-307. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. Impacted is confidentiality. The summary by CVE is:

changedetection.io's /login route checks the submitted password against a single PBKDF2-HMAC-SHA256 hash with no per-IP or per-session rate limiting, failed-attempt counter, or lockout (no rate-limiting library is present in requirements.txt). Because the entire application is protected by one shared password with no per-user accounts, a successful brute-force guess grants full administrative access, including the ability to view/regenerate the API token.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-71205 since 08/05/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.

By approaching the search of inurl:requirements.txt it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-53202). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• dgtlmoon

Name

• Changedetection.io

Version

• 0.55.7

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion