Issue 362: Django 6.1.3, 6.0.10, and 5.2.19 Security Releases

Django's security releases 6.1.3, 6.0.10, and 5.2.19 address six CVEs, including two server‑side request forgery (SSRF) vulnerabilities in GeoDjango where GDAL resolves URLs or files from GeoJSON CRS members and SpatialReference strings, and full mitigation requires GDAL 3.9+. For website owners running Django‑based sites, the SSRF flaws mean that malicious actors can craft GeoJSON payloads that force the server to fetch internal resources or external files, potentially exposing sensitive data or enabling further compromise. If your application uses GeoDjango for mapping, spatial queries, or imports of GeoJSON data, you are directly at risk until you upgrade both Django and the underlying GDAL library. Failure to patch could also trigger automated AI bots that scan for vulnerable endpoints, increasing unwanted traffic and abuse. **Actionable steps:** 1. **Upgrade immediately** to Django 6.1.3, 6.0.10, or 5.2.19 and ensure GDAL 3.9+ is installed; verify the versions via `python -m django --version` and `gdalinfo --version`. 2. **Update your llms.txt** to explicitly list the patched Django versions and GDAL requirement, e.g., `User‑Agent: *\nAllow: /` and add a comment `# Requires Django ≥6.1.3 & GDAL ≥3.9`. 3. **Deploy a bot‑tracking rule** in your llmscentral dashboard that flags any requests to `/geojson/` or `/spatial/` endpoints with unusual `Referer` or `User‑Agent` strings, enabling you to block or rate‑limit potential SSRF probing bots.