CVE-2026-6577

Received Received - Intake

Authentication Bypass in liangliangyy DjangoBlog logtracks Endpoint

Publication date: 2026-04-19

Last updated on: 2026-04-29

Assigner: VulDB

Description

A vulnerability was identified in liangliangyy DjangoBlog up to 2.1.0.0. The impacted element is an unknown function of the file owntracks/views.py of the component logtracks Endpoint. The manipulation leads to missing authentication. The attack can be initiated remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-04-19

Last Modified

2026-04-29

Generated

2026-07-06

AI Q&A

2026-04-19

EPSS Evaluated

2026-07-05

NVD

CVE-2026-6577

EUVD

EUVD-2026-23708

Affected Vendors & Products

Vendor	Product	Version / Range
liangliangyy	djangoblog	to 2.1.0.0 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-306	The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
CWE-287	When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Attack-Flow Graph

Executive Summary

This vulnerability exists in liangliangyy DjangoBlog up to version 2.1.0.0, specifically in an unknown function within the file owntracks/views.py of the logtracks Endpoint component.

The issue allows an attacker to bypass authentication due to manipulation, and the attack can be initiated remotely.

The exploit for this vulnerability is publicly available and might be used by attackers.

The vendor was contacted early about this disclosure but did not respond.

Impact Analysis

This vulnerability can lead to missing authentication, meaning unauthorized users could gain access to the system remotely.

Such unauthorized access could compromise the confidentiality, integrity, and availability of the affected system.

Given the CVSS scores (v3.1 BaseScore 7.3 and v2.0 BaseScore 7.5), the impact is considered high.

Hi! I’m here to help you understand CVE-2026-6577. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70