dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10184

HIGH · 8.2 CVSS v4.0 Published 2025-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
85/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The vulnerability allows any application installed on the device to read SMS/MMS data and metadata from the system-provided Telephony provider without permission, user interaction, or consent. The user is also not notified that SMS data is being accessed. This could lead to sensitive information disclosure and could effectively break the security provided by SMS-based Multi-Factor Authentication (MFA) checks. The root cause is a combination of missing permissions for write operations in several content providers (com.android.providers.telephony.PushMessageProvider, com.android.providers.telephony.PushShopProvider, com.android.providers.telephony.ServiceNumberProvider), and a blind SQL injection in the update method of those providers.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Android Telephony content providers (PushMessageProvider, PushShopProvider, ServiceNumberProvider) lack permission checks on write operations combined with blind SQL injection in their update methods, enabling any installed application to read SMS/MMS data and metadata without user consent, notification, or runtime permissions.

MitigationApply Android OS security patches from Google/device OEMs to address the missing permission enforcement in Telephony providers; consider migrating away from SMS-based MFA to more secure authentication methods.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android security patch level
    Go to Settings > About Phone > Security Patch Level (or Software Information > Security Patch Level on some devices). Compare the date to the patch release date for this CVE.
    Affected if The security patch level is earlier than the month the CVE fix was released, indicating the device has not received the security update that addresses this vulnerability.
  2. Verify SMS runtime permission enforcement
    Check if apps can read SMS without the runtime permission being granted. Attempt to observe if any app has accessed SMS content or if apps in the appops or SMS database have access when they should not.
    Affected if Apps have accessed SMS/MMS data without user-granted runtime permission, indicating the permission bypass is being exploited.
  3. Audit installed apps for suspicious SMS provider access
    Review installed applications, particularly those that should not have a need for SMS access, and check if any have unexpectedly been granted or acquired access to the Telephony content providers (PushMessageProvider, PushShopProvider, ServiceNumberProvider).
    Affected if An app has access to SMS/MMS data despite not having the appropriate Android runtime permission (READ_SMS, RECEIVE_SMS, SEND_SMS, etc.) granted by the user.
  4. Check for unexpected SMS database queries
    Monitor or review system logs (logcat) for queries to content://pms/ or similar Telephony provider URIs from applications that lack SMS permissions.
    Affected if Queries to SMS content providers originate from apps without the android.permission.READ_SMS or android.permission.RECEIVE_SMS permissions.

The device is likely affected if the security patch level predates the CVE fix and any app can access SMS/MMS data without user-granted runtime permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Android OS security patches from Google/device OEMs to address the missing permission enforcement in Telephony providers; consider migrating away from SMS-based MFA to more secure authentication methods.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10184 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data