CVE-2026-68923: CWE-352: Cross-Site Request Forgery (CSRF) in MobSF Mobile-Security-Framework-MobSF
A Cross-Site Request Forgery (CSRF) vulnerability exists in MobSF Mobile-Security-Framework-MobSF versions prior to 4.5.1 due to improper middleware configuration. This allows remote attackers to trick logged-in users into submitting unauthorized POST requests to sensitive endpoints, potentially leading to unauthorized actions such as deleting scans, uploading or downloading applications, changing passwords, or managing user accounts. The issue is resolved in version 4.5.1.
AI Analysis
Technical Summary
MobSF Mobile-Security-Framework-MobSF versions before 4.5.1 improperly configure Django middleware by placing django.middleware.csrf.CsrfViewMiddleware only in the deprecated MIDDLEWARE_CLASSES setting and omitting it from the active MIDDLEWARE tuple. This misconfiguration disables CSRF protection on authenticated web endpoints including /delete_scan/, /upload/, /download_scan/, /change_password/, /create_user/, and /delete_user/. As a result, a remote attacker can cause a logged-in victim to perform unintended POST requests, leading to unauthorized modification or deletion of data and user management actions. The vulnerability is fixed in version 4.5.1.
Potential Impact
Exploitation allows an attacker to perform unauthorized actions with the privileges of the victim user by tricking them into submitting cross-site POST requests. This can lead to deletion of scans, unauthorized upload or download of applications, password changes, and user account management without the victim's consent. There is no impact on confidentiality but a high impact on integrity. Availability is not affected.
Mitigation Recommendations
Upgrade MobSF Mobile-Security-Framework-MobSF to version 4.5.1 or later, where the CSRF middleware is correctly configured in the active MIDDLEWARE tuple. No other mitigation is indicated. Patch status is confirmed fixed in 4.5.1.
CVE-2026-68923: CWE-352: Cross-Site Request Forgery (CSRF) in MobSF Mobile-Security-Framework-MobSF
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in MobSF Mobile-Security-Framework-MobSF versions prior to 4.5.1 due to improper middleware configuration. This allows remote attackers to trick logged-in users into submitting unauthorized POST requests to sensitive endpoints, potentially leading to unauthorized actions such as deleting scans, uploading or downloading applications, changing passwords, or managing user accounts. The issue is resolved in version 4.5.1.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/mobsf/Mobile-Security-Framework-MobSFRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
MobSF Mobile-Security-Framework-MobSF versions before 4.5.1 improperly configure Django middleware by placing django.middleware.csrf.CsrfViewMiddleware only in the deprecated MIDDLEWARE_CLASSES setting and omitting it from the active MIDDLEWARE tuple. This misconfiguration disables CSRF protection on authenticated web endpoints including /delete_scan/, /upload/, /download_scan/, /change_password/, /create_user/, and /delete_user/. As a result, a remote attacker can cause a logged-in victim to perform unintended POST requests, leading to unauthorized modification or deletion of data and user management actions. The vulnerability is fixed in version 4.5.1.
Potential Impact
Exploitation allows an attacker to perform unauthorized actions with the privileges of the victim user by tricking them into submitting cross-site POST requests. This can lead to deletion of scans, unauthorized upload or download of applications, password changes, and user account management without the victim's consent. There is no impact on confidentiality but a high impact on integrity. Availability is not affected.
Mitigation Recommendations
Upgrade MobSF Mobile-Security-Framework-MobSF to version 4.5.1 or later, where the CSRF middleware is correctly configured in the active MIDDLEWARE tuple. No other mitigation is indicated. Patch status is confirmed fixed in 4.5.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-31T21:04:04.041Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a849b5fc6e8be03328d6f5a
Added to database: 08/18/2026, 17:50:23 UTC
Last enriched: 08/18/2026, 18:06:14 UTC
Last updated: 08/18/2026, 22:24:35 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.