MobSF's CSRF checks not enforced after Django migration

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-68923: 0.26% estimated exploitation activity in the next 30 days; percentile 18.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Django's CsrfViewMiddleware exists only in the deprecated MIDDLEWARECLASSES (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: 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=Lax allows form-based top-level navigation to send the session cookie Affected Component 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 "Recent Scans". 3. Open the following HTML file in the same browser (simulates visiting…

Published by the source

18 Aug 2026, 18:01 UTC

Last modified by the source

18 Aug 2026, 18:01 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3p54-567p-2wpr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-68923

Advisory: MobSF's CSRF checks not enforced after Django migration
IDs: CVE-2026-68923, GHSA-3p54-567p-2wpr
Record: https://patchnext.com/advisories/cve-2026-68923 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mobsf 4.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mobsf: affected < 4.5.1; fixed in 4.5.1

## Suggested inspection (read-only)
- `python -m pip show mobsf`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mobsf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3p54-567p-2wpr (GitHub-reviewed advisory GHSA-3p54-567p-2wpr lists affected ranges: PyPI mobsf >=0 <4.5.1)

Commands are suggestions: review each one before running it.