DjangoBlog Stored XSS via Comment Reactions
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
DjangoBlog commit d186b1c through commit 6134ed6 contains a stored cross-site scripting flaw (CWE-79) in comment reactions. An authenticated OAuth user with low privileges can set a display name that is written unescaped into a page attribute, so script runs in the browsers of article visitors who view the reacted comment, with user interaction required.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
DjangoBlog commit d186b1c through commit 6134ed6 contains a stored cross-site scripting vulnerability that allows authenticated OAuth users to inject script via an unescaped nickname in comment reactions. Attackers can set their OAuth display name to a payload closing the single-quoted data-reactions attribute, then react to a comment to execute script in article visitors' browsers.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
No affected products listed by the sources yet.
Remediation
The sources list no fixed version for DjangoBlog commit d186b1c through commit 6134ed6.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Timeline
- 2026-11-13 Threatist record created from CVE-2026-129156
- 2026-11-13 Alias added: GHSA-cqpq-mfhw-4pgq
- 2026-11-13 CISA SSVC decision points changed
References
Other 4
- https://github.com/liangliangyy/DjangoBlog/issues/1030
- https://github.com/liangliangyy/DjangoBlog/blob/6134ed63079de676b271af31de4dd40264d17c52/oauth/views.py#L102-L112
- https://github.com/liangliangyy/DjangoBlog/blob/6134ed63079de676b271af31de4dd40264d17c52/templates/comments/tags/comment_item_modern.html#L76
- https://github.com/liangliangyy/DjangoBlog/blob/6134ed63079de676b271af31de4dd40264d17c52/blog/templatetags/blog_tags.py#L162-L164
More liangliangyy vulnerabilities
- TI-2026-05767 liangliangyy DjangoBlog Amap API Call views.py hard-coded key CVSS 4.0MEDIUM 6.9
- TI-2026-05766 liangliangyy DjangoBlog Clean Endpoint views.py missing authentication CVSS 4.0MEDIUM 6.9
- TI-2026-05764 liangliangyy DjangoBlog logtracks Endpoint views.py missing authentication CVSS 4.0MEDIUM 6.9
- TI-2026-05797 liangliangyy DjangoBlog Setting settings.py hard-coded credentials CVSS 4.0MEDIUM 6.3
- TI-2026-05796 liangliangyy DjangoBlog views.py form_valid improper authorization CVSS 4.0MEDIUM 5.3
- TI-2026-05763 liangliangyy DjangoBlog WeChat Bot commonapi.py CommandHandler command injection CVSS 4.0MEDIUM 5.3
Sources
- CVE-2026-129156 · CVE Program
- CVE-2026-129156 · NVD
- FIRST EPSS
- GHSA-cqpq-mfhw-4pgq · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences