CVE-2026-6576 | liangliangyy DjangoBlog up to 2.1.0.0 WeChat Bot Interface commonapi.py CommandHandler Source command injection

VDB-358211 · SUBMIT #790281 · CVE-2026-6576 LIANGLIANGYY DJANGOBLOG UP TO 2.1.0.0 WECHAT BOT INTERFACE COMMONAPI.PY COMMANDHANDLER SOURCE COMMAND INJECTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.7 $0-$5k 2.38+ Summaryinfo A vulnerability was found in liangliangyy DjangoBlog up to 2.1.0.0. It has been rated as critical. The impacted element is the function CommandHandler of the file servermanager/api/commonapi.py of the component WeChat Bot Interface. The manipulation of the argument Source leads to command injection. This vulnerability is documented as CVE-2026-6576. The attack can be initiated remotely. Additionally, an exploit exists. The vendor was contacted early about this disclosure but did not respond in any way. Detailsinfo A vulnerability, which was classified as critical, has been found in liangliangyy DjangoBlog up to 2.1.0.0. This issue affects the function CommandHandler of the file servermanager/api/commonapi.py of the component WeChat Bot Interface. The manipulation of the argument source with an unknown input leads to a command injection vulnerability. Using CWE to declare the problem leads to CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-6576. The exploitation is known to be easy. The attack may be initiated remotely. Technical details as well as a public exploit are known. The attack technique deployed by this issue is T1202 according to MITRE ATT&CK. The exploit is available at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Type Content Management System Vendor liangliangyy Name DjangoBlog Version 2.1.0 CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.3 VulDB Meta Temp Score: 5.7 VulDB Base Score: 6.3 VulDB Temp Score: 5.7 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Command injection CWE: CWE-77 / CWE-74 / CWE-707 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Access: Public Status: Proof-of-Concept Download: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/19/2026 Advisory disclosed 04/19/2026 +0 days VulDB entry created 04/19/2026 +0 days VulDB entry last update Sourcesinfo Advisory: github.com Status: Not defined CVE: CVE-2026-6576 (🔒) GCVE (CVE): GCVE-0-2026-6576 GCVE (VulDB): GCVE-100-358211 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 04/19/2026 07:16 Changes: 04/19/2026 07:16 (59) Complete: 🔍 Submitter: Dem0 Cache ID: 99:51A:101 Submitinfo Accepted Submit #790281: liangliangyy DjangoBlog <= 2.1.0.0 Command Injection (by Dem0) Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸