Cross-Site Request Forgery (CSRF) in mobsf (CVE-2026-68923)
Summary
Vulnerability in mobsf (CVE-2026-68923). Data can be tampered with by attackers. Exploitable via CsrfViewMiddleware. Mitigation: upgrade to 4.5.1 or later.
Original description
The description as published by the source.
Summary
Django's CsrfViewMiddleware exists only in the deprecated MIDDLEWARE_CLASSES (ignored since Django 2.0). The active MIDDLEWARE tuple does not include it. All authenticated web POST endpoints (delete scan, upload, download APK, change password, manage users) accept requests without CSRF tokens.
Verified Impact
This was verified by actually deleting a real scan from the running server using only a session cookie — no CSRF token was required:
$ curl -s -b cookies.txt -X POST "http://127.0.0.1:8000/delete_scan/" \
-d "md5=68e76627798d62555d5287f4488a32c7&scan_type=apk"
{"deleted": "yes"}
The scan was removed from the database. This attack works from any website via HTML form auto-submission because:
- No CSRF token is validated (middleware absent)
- Cookie
SameSite=Laxallows form-based top-level navigation to send the session cookie
Affected Component
File: mobsf/MobSF/settings.py (Lines 206-212)
MIDDLEWARE = (
'mobsf.MobSF.views.api.api_middleware.RestApiAuthMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
# MISSING: 'django.middleware.csrf.CsrfViewMiddleware'
)
Steps to Reproduce
1. Start MobSF v4.4.6 and log in at http://127.0.0.1:8000/login/ (creds: mobsf/mobsf).
2. Upload and scan any APK to create a scan entry. Note the MD5 hash from "…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-68923 has been found in mobsf.
Attackers can target a specific entry point like CsrfViewMiddleware over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade mobsf to 4.5.1 or later.
If unsure, ask your IT team or search "mobsf CVE-2026-68923" on the vendor's site.
CVE-2026-68923 (mobsf) — CWE-352 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: CsrfViewMiddleware / MIDDLEWARE_CLASSES / MIDDLEWARE
Patched: 4.5.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in mobsf. Attackers reach the vulnerable code path via CsrfViewMiddleware without authentication.
Check the vendor advisory for the affected versions of mobsf. Attack surface: CsrfViewMiddleware / MIDDLEWARE_CLASSES / MIDDLEWARE.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 4.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mobsf' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mobsf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mobsfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mobsf to 4.5.1ステージング環境で 4.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。