Djangoblog
Approved changes feed: RSS · Atom
cpe:2.3:a:liangliangyy:djangoblog:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Liangliangyy (4d26dde7-9119-5823-8302-2b0ebaf7062c) |
|---|---|
| Product | Djangoblog (e1342f11-3849-5b9e-91d6-54255ff2d474) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-6611 |
vulnerable | 2026-06-08 08:07:04.937401 |
liangliangyy DjangoBlog File Upload Endpoint settings.py hard-coded key
LOW (3.1)
A vulnerability was found in liangliangyy DjangoBlog up to 2.1.0.0. This affects an unknown function of the file djangoblog/settings.py of the component File Upload Endpoint. Performing a manipulation of the argument SECRET_KEY results in use of hard-coded cryptographic key
. Remote exploitation of the attack is possible. The attack's complexity is rated as high. The exploitability is reported as difficult. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
Published: 2026-04-20T06:00:18.066Z
Updated: 2026-04-20T16:00:23.582Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6610 |
vulnerable | 2026-06-08 08:07:04.937101 |
liangliangyy DjangoBlog Setting settings.py hard-coded credentials
LOW (3.7)
A vulnerability has been found in liangliangyy DjangoBlog up to 2.1.0.0. The impacted element is an unknown function of the file djangoblog/settings.py of the component Setting Handler. Such manipulation of the argument USER/PASSWORD leads to hard-coded credentials. The attack may be launched remotely. The attack requires a high level of complexity. The exploitability is regarded as difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Published: 2026-04-20T05:45:18.671Z
Updated: 2026-04-20T16:03:06.598Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6609 |
vulnerable | 2026-06-08 08:07:04.936684 |
liangliangyy DjangoBlog views.py form_valid improper authorization
MEDIUM (6.3)
A flaw has been found in liangliangyy DjangoBlog up to 2.1.0.0. The affected element is the function form_valid of the file oauth/views.py. This manipulation of the argument oauthid causes improper authorization. The attack may be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Published: 2026-04-20T05:30:16.620Z
Updated: 2026-04-20T13:51:42.600Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6580 |
vulnerable | 2026-06-08 08:07:04.909159 |
liangliangyy DjangoBlog Amap API Call views.py hard-coded key
HIGH (7.3)
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.
Published: 2026-04-19T22:15:12.387Z
Updated: 2026-04-20T14:55:13.830Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6579 |
vulnerable | 2026-06-08 08:07:04.908758 |
liangliangyy DjangoBlog Clean Endpoint views.py missing authentication
MEDIUM (6.5)
A weakness has been identified in liangliangyy DjangoBlog up to 2.1.0.0. This impacts an unknown function of the file blog/views.py of the component Clean Endpoint. This manipulation causes missing authentication. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Published: 2026-04-19T22:00:17.503Z
Updated: 2026-04-20T15:18:38.633Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6578 |
vulnerable | 2026-06-08 08:07:04.908479 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6577 |
vulnerable | 2026-06-08 08:07:04.908166 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6576 |
vulnerable | 2026-06-08 08:07:04.907591 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.