. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 20 Apr 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Liangliangyy
Liangliangyy djangoblog |
|
| Vendors & Products |
Liangliangyy
Liangliangyy djangoblog |
|
| Metrics |
ssvc
|
Sun, 19 Apr 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A security vulnerability has been detected in liangliangyy DjangoBlog up to 2.1.0.0. Affected is an unknown function of the file owntracks/views.py of the component Amap API Call Handler. Such manipulation of the argument key leads to use of hard-coded cryptographic key . The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way. | |
| Title | liangliangyy DjangoBlog Amap API Call views.py hard-coded key | |
| Weaknesses | CWE-320 CWE-321 |
|
| References |
| |
| Metrics |
cvssV2_0
|
Status: PUBLISHED
Assigner: VulDB
Published:
Updated: 2026-04-20T14:55:13.830Z
Reserved: 2026-04-19T05:11:05.496Z
Link: CVE-2026-6580
Updated: 2026-04-20T14:46:54.198Z
Status : Deferred
Published: 2026-04-19T23:16:33.697
Modified: 2026-04-29T01:00:01.613
Link: CVE-2026-6580
No data.
OpenCVE Enrichment
Updated: 2026-04-20T14:58:34Z