CWE-925: Improper Verification of Intent by Broadcast Receiver
Also known as: Intent Spoofing
The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.
Last updated
Overview
Certain types of Intents, identified by action string, can only be broadcast by the operating system itself, not by third-party applications. However, when an application registers to receive these implicit system intents, it is also registered to receive any explicit intents. While a malicious application cannot send an implicit system intent, it can send an explicit intent to the target application, which may assume that any received intent is a valid implicit system intent and not an explicit intent from another application. This may lead to unintended behavior.
Real-world CVEs
4 recorded CVEs are caused by CWE-925 (Improper Verification of Intent by Broadcast Receiver). The highest-severity and most recent are shown first. 2 new CWE-925 CVEs have been recorded so far in 2026.
- CVE-2024-10576
Unauthorized factory reset of Infinix devices
Critical · CVSS 9.4 · EPSS 6th2024-12-04 - CVE-2023-44126
Call management - Implicit intents disclose telephony data such as phone numbers, call states, contacts
Medium · CVSS 5.5 · EPSS 3th2023-09-27 - CVE-2026-33173
Rails Active Storage has possible content type bypass via metadata in direct uploads
Medium · CVSS 5.3 · EPSS 34th2026-03-23 - CVE-2026-21106Medium · CVSS 5.1 · EPSS 4th2026-09-09
Common consequences
What can happen when CWE-925 is exploited.
Gain Privileges or Assume Identity
Affects: Integrity
Another application can impersonate the operating system and cause the software to perform an unintended action.
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
Applies to
Technologies
How to prevent it
Practical mitigations for CWE-925, grouped by where in the lifecycle they apply.
Before acting on the Intent, check the Intent Action to make sure it matches the expected System action.
How to detect it
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness: High
Code examples
MITRE examples of the weakness in code.
The following example demonstrates the weakness.
Vulnerable example
<manifest package="com.example.vulnerableApplication">
<application>
...
...
<receiver android:name=".ShutdownReceiver">
<intent-filter>
<action android:name="android.intent.action.ACTION_SHUTDOWN" />Vulnerable example
...
...
@Override
mainActivity.saveLocalData();Attack input
window.location = examplescheme://method?parameter=valueIllustrative examples
Real CVEs that MITRE cites as examples of this weakness.
- CVE-2025-20972 — Mobile app store does not properly verify the intent by the broadcast receiver, allowing local attackers to write arbitrary files
- CVE-2024-10576 — Mobile device has an application that exposes a broadcast received that allows local attackers to force a factory reset
Terminology & mappings
Alternate terms
- Intent Spoofing
Attack patterns
CAPEC attack patterns that exploit this weakness.
Frequently asked questions
Common questions about CWE-925.
- What is CWE-925?
- The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.
- What CVEs are caused by CWE-925?
- 4 recorded CVEs are attributed to CWE-925, including CVE-2024-10576, CVE-2023-44126 and CVE-2026-33173.
- How do you prevent CWE-925?
- Before acting on the Intent, check the Intent Action to make sure it matches the expected System action.
- How is CWE-925 detected?
- Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
- What are the consequences of CWE-925?
- Exploiting CWE-925 can lead to: Gain Privileges or Assume Identity.
- Is CWE-925 actively exploited?
- 4 recorded CVEs are caused by CWE-925; none are currently in CISA's KEV catalog of actively exploited flaws.
Sources
References
- MITRE CWE definition (CWE-925) (opens in a new tab)
- CWE-925 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Track CWE-925 CVEs
Get an alert when a new CWE-925 CVE affects your products, with AI-written analysis and remediation steps.