---
title: "CWE-925: Improper Verification of Intent by Broadcast Receiver"
url: https://radicalnotion.ai/cwe/cwe-925
type: cwe
description: "The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-925: Improper Verification of Intent by Broadcast Receiver

- **Abstraction:** Variant
- **Structure:** Simple
- **Status:** Incomplete
- **CVEs with this as primary weakness:** 19
- **Of those, in CISA KEV:** 0
- **New in 2026:** 3
- **CWE catalog version:** 4.21

## Description

The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.

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.

## Alternate terms

- Intent Spoofing

## Modes of introduction

| Phase | Note |
| --- | --- |
| Architecture and Design | - |

## Applicable platforms

**Technologies:** Mobile (Undetermined)

## Common consequences

| Scope | Impact | Note |
| --- | --- | --- |
| Integrity | Gain Privileges or Assume Identity | Another application can impersonate the operating system and cause the software to perform an unintended action. |

## Potential mitigations

### Architecture and Design

Before acting on the Intent, check the Intent Action to make sure it matches the expected System action.

## Detection methods

### 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

## Demonstrative examples

### Example 1

The following example demonstrates the weakness.

Bad code:

```xml
<manifest package="com.example.vulnerableApplication">
    <application>
    ...
        <receiver android:name=".ShutdownReceiver">
            <intent-filter>
                <action android:name="android.intent.action.ACTION_SHUTDOWN" />
            </intent-filter>
        </receiver>

    ...

    </application>
</manifest>
```

Bad code:

```java
...
IntentFilter filter = new IntentFilter(Intent.ACTION_SHUTDOWN);
BroadcastReceiver sReceiver = new ShutDownReceiver();
registerReceiver(sReceiver, filter);
...

public class ShutdownReceiver extends BroadcastReceiver {
    @Override
    public void onReceive(final Context context, final Intent intent) {
        mainActivity.saveLocalData();
        mainActivity.stopActivity();
    }
}
```

Attack code:

```java
window.location = examplescheme://method?parameter=value
```

## Observed examples

| CVE | Description |
| --- | --- |
| 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 |

## Real CVEs with this weakness (sample of 12 of 19)

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2024-10576 | Unauthorized factory reset of Infinix devices | critical | 9.4 | - | No | 2024-12-04 |
| CVE-2023-42543 | - | high | 7.5 | - | No | 2023-11-07 |
| CVE-2026-20988 | - | medium | 6.8 | - | No | 2026-03-16 |
| CVE-2025-20972 | - | medium | 6.2 | - | No | 2025-05-07 |
| CVE-2024-34601 | - | medium | 5.9 | - | No | 2024-07-02 |
| CVE-2024-20852 | - | medium | 5.9 | - | No | 2024-04-02 |
| CVE-2025-20951 | - | medium | 5.5 | - | No | 2025-04-08 |
| CVE-2024-20870 | - | medium | 5.5 | - | No | 2024-05-07 |
| CVE-2023-44126 | Call management - Implicit intents disclose telephony data such as phone numbers, call states, contacts | medium | 5.5 | - | No | 2023-09-27 |
| CVE-2026-33173 | Rails Active Storage has possible content type bypass via metadata in direct uploads | medium | 5.3 | - | No | 2026-03-23 |
| CVE-2026-21106 | - | medium | 5.1 | - | No | 2026-09-09 |
| CVE-2025-21040 | - | medium | 5.1 | - | No | 2025-09-03 |

## Related attack patterns (CAPEC)

- [CAPEC-499](https://radicalnotion.ai/capec/capec-499): Android Intent Intercept

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-940](https://radicalnotion.ai/cwe/cwe-940) | Improper Verification of Source of a Communication Channel |

## Frequently asked questions

### 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?

19 recorded CVEs are attributed to CWE-925, including CVE-2024-10576, CVE-2023-42543 and CVE-2026-20988.

### 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?

19 recorded CVEs are caused by CWE-925; none are currently in CISA's KEV catalog of actively exploited flaws.

Primary source: [MITRE CWE](https://cwe.mitre.org/data/definitions/925.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/cwe/cwe-925). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
