What happened
A public source linked this CVE to an advisory or demonstration repository. Review the original reference before use.
Affected versions
Unknown product: See original advisory Fixed: See vendor advisory.
Why it matters
This source correlation may provide earlier visibility while structured CVE metadata is still being updated.
Detection & mitigation
- Review the original advisory and validate affected versions.
- Apply vendor-provided updates or mitigations when available.
Public PoC references
RepositoryAuthorFirst seenReference
PoC-in-GitHub · aeyesec/CVE-2022-34265PoC for CVE-2022-34265 (Django)★ 124aeyesec2022-07-07CandidatePoC-in-GitHub · traumatising/CVE-2022-34265CVE-2022-34265 Vulnerability★ 3traumatising2022-07-13CandidatePoC-in-GitHub · ZhaoQi99/CVE-2022-34265PoC for CVE-2022-34265★ 4ZhaoQi992022-08-24CandidatePoC-in-GitHub · lnwza0x0a/CTF_Django_CVE-2022-34265★ 1lnwza0x0a2022-09-08CandidatePoC-in-GitHub · CyberCTF/vulhub-django-cve-2022-34265Vulhub django/CVE-2022-34265: Django Trunc and Extract SQL Injection (CVE-2022-34265), run with Isoloom★ 0CyberCTF2026-10-08CandidateSource timeline
Discovered through PoC-in-GitHubView source ↗
Record history
Record created from the first normalized source observation.
Metadata and source references refreshed.