agentleFS
ashrafiucseashrafiucse/security-audit-skills/skills/django-security/SKILL.md

django-security

Skill2 starsChanged 49 days agoMITView on GitHub

Audits Django (Python) applications for framework-specific vulnerabilities — raw()/extra() SQL injection, mark_safe and |safe filter XSS, SSTI via Template() with user strings, ModelForm fields='__all__' mass assignment, settings misconfigurations (DEBUG=True, ALLOWED_HOSTS=['*'], insecure cookie flags, hardcoded SECRET_KEY), missing login_required/permission checks (IDOR), weak password hashers, and django-cors-headers wildcards. Use when the project has manage.py, settings.py, or Django in requirements.

  • Reads credentials

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use configure-ecc, nuxt4-patterns and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • royaluniondesign-sysSkill

    configure-ecc

    Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

    Also in 12 projects that use this

  • loulanyueSkill

    nuxt4-patterns

    Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.

    Also in 10 projects that use this

  • RojiosSkill

    defi-amm-security

    Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.

    Also in 8 projects that use this

  • ronmkrSkill

    quarkus-security

    Quarkus Security best practices for authentication, authorization, JWT/OIDC, RBAC, input validation, CSRF, secrets management, and dependency security.

    Also in 6 projects that use this

  • TironFoxSkill

    agent-payment-x402

    Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.

    Also in 6 projects that use this

  • TironFoxSkill

    openclaw-persona-forge

    为 OpenClaw AI Agent 锻造完整的龙虾灵魂方案。根据用户偏好或随机抽卡, 输出身份定位、灵魂描述(SOUL.md)、角色化底线规则、名字和头像生图提示词。 如当前环境提供已审核的生图 skill,可自动生成统一风格头像图片。 当用户需要创建、设计或定制 OpenClaw 龙虾灵魂时使用。 不适用于:微调已有 SOUL.md、非 OpenClaw 平台的角色设计、纯工具型无性格 Agent。 触发词:龙虾灵魂、虾魂、OpenClaw 灵魂、养虾灵魂、龙虾角色、龙虾定位、 龙虾剧本杀角色、龙虾游戏角色、龙虾 NPC、龙虾性格、龙虾背景故事、 lobster soul、lobster character、抽卡、随机龙虾、龙虾 SOUL、gacha。

    Also in 5 projects that use this

The file

Files
SKILL.md

Django Security

Step 0 — Detect

rg -n "^[Dd]jango" -g 'requirements*.txt' -g 'pyproject.toml' -g 'Pipfile*' -g 'poetry.lock'
ls manage.py **/settings.py 2>/dev/null || rg --files -g 'settings.py' | head -3

Record Django version, auth setup (django.contrib.auth vs custom), and deployment target hints.

Step 1 — Settings

rg -n "DEBUG|ALLOWED_HOSTS|SECRET_KEY|CSRF_COOKIE|SESSION_COOKIE|SECURE_" -g 'settings*.py' -g 'settings/*.py'
FindingSeverity
Hardcoded SECRET_KEY (not env)High (Critical if repo is public — session forgery, password-reset tokens)
DEBUG = True in prod settingsHigh (stack traces; historically settings disclosure)
ALLOWED_HOSTS = ['*']Medium → host-header poisoning of password-reset links (High when reset flows exist)
CSRF_COOKIE_SECURE / SESSION_COOKIE_SECURE False/absentMedium
SECURE_SSL_REDIRECT absent behind plain HTTPMedium
PASSWORD_HASHERS with MD5/SHA1 hasherCritical (weak password storage)
django-cors-headers: CORS_ALLOW_ALL_ORIGINS=True (+ credentials)Medium/Critical

Step 2 — SQL injection

rg -n "\.raw\(|\.extra\(|cursor\.execute" --type py
  • Model.objects.raw(f"...{request...}") / .raw("... %s" % var) → Critical
  • .extra(where=[f"...{...}"]) → Critical
  • ORM field lookups (filter(name__icontains=q)) → safe, note as positive

Step 3 — XSS / template injection

rg -n "mark_safe\s*\(" --type py
rg -n "\|safe\b" -g '*.html' -g '*.htm'
rg -n "Template\(|Engine\(\)\.from_string" --type py

Census, don't sample: count and disposition EVERY hit. (Do not combine these into one command — --type py and a -g '*.html' glob in the same invocation silently drop the .py hits, i.e. every mark_safe in views.) Severity by privilege direction per ../injection-flaws/SKILL.md (XSS table): unprivileged author → privileged viewer = Critical.

  • mark_safe(user_data) → reflected High; stored unprivileged→staff (moderation/support/grading) Critical
  • {{ var|safe }} in templates on user-derived vars → same triage
  • autoescape=False in Template()/loader options → High
  • Template(user_string) (string built from input) → SSTI, Critical

Step 4 — Mass assignment

rg -n "fields = '__all__'|exclude = .*ModelForm|modelform_factory" --type py
  • ModelForm with fields = '__all__' on models with role/flag columns (is_superuser, is_staff, role, balance) → High/Critical
  • Model(**request.POST.dict()) / manual form = X(request.POST) without restricting → same
  • Fix: explicit field allowlists; request.POST is user-controlled wholesale.

Step 5 — Authorization

rg -n "login_required|LoginRequiredMixin|permission_required|@user_passes_test" --type py
rg -n "def (view|detail|edit|delete)" --type py | head -20
  • Object views without ownership check (Model.objects.get(pk=request.GET['id']) returned directly) → IDOR, High
  • Class-based views missing LoginRequiredMixin on data mutation → High
  • @staff_member_required on endpoints exposing PII → verify minimum role

Step 6 — Files & misc

rg -n "request\.FILES|FileField|MEDIA" --type py
rg -n "pickle|eval\(|exec\(" --type py | head
  • Uploads with original filenames served from MEDIA (executable content + Apache/nginx PHP exec) → Medium/High
  • pickle in custom session/queue serialization → Critical
  • django-debug-toolbar in non-dev requirements → Medium
  • File responses built from request paths → traversal, High

Reporting

Severity table above; fixes are one-liners mostly (field allowlists, decorators, settings flags). Note ORM usage as a positive control. Dependency CVEs via ../dependency-vulns/SKILL.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.