Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious co-resident app on device
-
ExploitAccess insecurely-permissioned Simple Contacts notes database
-
ImpactRead and tamper with victim's contact notes
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local presence on the device running Simple Contacts Pro versionCode 107 - specifically a second device user profile or a co-resident app that leverages the application's insecure permissions on its notes database to read and write another user's notes. No special privilege or permission grant is needed and no user interaction is described, but the attacker must already be on the device; the exact exported component or file-permission setting that is misconfigured is not described in the available sources, and no fixed version is provided. This limits realistic risk to multi-user devices or devices where a malicious app can be installed, not to remote network attackers. |
| Impact | The input CVSS of 9.1 is driven by an AV:N (network) vector, but this conflicts with the described mechanism: 'insecure permissions' in an Android application (Simple Contacts Pro, a SimpleMobileTools/F-Droid app per the references) that let one user or co-resident app read and write another user's contact-notes database. Access-control flaws of this kind (CWE-284) are almost always exercised locally on the device, so the network vector appears inflated - verify with the vendor/advisory before treating this as remotely reachable. Setting that aside, the decision signals are consistent and point to a genuine priority on affected devices: SSVC reports Exploitation=poc, Automatable=yes, and Technical Impact=total, and the vuln.today Decision label is act_now. There is no CISA KEV listing and no EPSS score in the supplied data, so there is no confirmation of in-the-wild or widespread exploitation - the picture is 'low-complexity, automatable, PoC available, but local and not confirmed exploited.' Net: treat as act_now for deployments of the affected build, but the real-world blast radius is bounded by the local attack surface and the product's limited footprint rather than the headline 9.1. |
| Exploit ScenarioDerived | A malicious application installed on the same device, or a secondary device user, abuses the insecurely-permissioned notes database in Simple Contacts Pro (versionCode 107) to read and modify another user's contact notes without being granted any permission. A public PoC reference exists (fdroid advisory and GitHub issue), and SSVC rates the technique automatable with total technical impact. Exploitation is low-complexity but requires local presence on the device. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Simple Contacts Pro (SimpleMobileTools/Simple-Contacts, distributed via F-Droid) at versionCode 107 ships with insecure permissions on its notes database, letting a second device user profile or a co-resident application read and write notes belonging to another user without any privilege grant or user interaction. The trigger is local rather than network-based: the input CVSS vector claims AV:N and a 9.1 score, but the mechanism described - an Android app's private note store being accessible to another principal on the same device - requires the attacker to already be present on the device, which is why our assessment re-scores it as AV:L with C:H/I:H. Priority is act_now under vuln.today triage, with SSVC recording a proof-of-concept and total technical impact, while CISA KEV contains no entry for this CVE; the SSVC 'poc' status indicates a public proof-of-concept reference exists, but it is not verified as working exploit code, and no fixed version is provided in the available sources.
RemediationAI
No vendor-released patch or fixed versionCode is identified in the available sources, so upgrading cannot yet be prescribed; track the project repository at https://github.com/SimpleMobileTools/Simple-Contacts, issue https://github.com/kanytu/Simple-Contacts/issues/628 and the advisory at https://github.com/FFG0d/fdroid-android-advisories/blob/main/advisories/CVE-2026-107015-CVE-2026-107016.md for a patched build, and treat any versionCode above 107 as unverified until the vendor states otherwise. Until a fix ships, the effective controls follow from the local attack precondition: run Simple Contacts Pro only on single-user devices with secondary user profiles and guest accounts disabled (trade-off: other apps lose profile isolation and shared-device use on that handset), and avoid installing untrusted or sideloaded applications alongside it, since any co-resident app is the other exploitation path to the notes database (trade-off: restricts app sourcing but does not stop a determined local attacker). Where the notes data is sensitive, migrating the contacts and notes off this build and uninstalling it removes exposure entirely. Because triage is set to act_now with a proof-of-concept indicated and total technical impact, these constraints should be applied immediately rather than deferred pending a release.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-284 (Improper Access Control) in an Android application from the Simple Mobile Tools family, per the cveorg references to SimpleMobileTools/Simple-Contacts and an F-Droid advisory bundle covering CVE-2026-107015 and CVE-2026-107016. Android isolates application data by per-app Linux UID, so a note database normally becomes reachable by another principal only when file permissions, a content provider export setting, or an equivalent access-control decision is misconfigured; the sources do not state which exported component or permission setting is at fault, so the precise trigger is not described in the available sources. The CPE data supplied is a placeholder (cpe:2.3:a:n/a:n/a) and the ENISA EUVD affected-version record reads 'n/a n/a', so product identity rests on the cveorg repository and advisory references rather than on structured CPE matching, and the affected build is identified only as versionCode 107. Because exploitation is confined to a device that already hosts the app, the practical attack surface is multi-user Android configurations (secondary user profiles, guest sessions) and devices on which an untrusted app can be installed, not remote network reach.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Insecure Android permissions require a co-resident app or second device user, so AV:L; no privilege grant needed (PR:N); read/write of notes yields C:H/I:H with no availability impact.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
2DescriptionCVE.org
Insecure permissions in Simple Contacts Pro versionCode 107 allow unauthorized attackers to write and read notes in another user's' note database.
Articles & Coverage 1
Executive ViewAI
A critical local vulnerability in Simple Contacts Pro (versionCode 107) allows a co-resident app or second user profile to read and write notes belonging to another user on the same Android device without any privilege grant or user interaction. Leadership should care because this threatens the confidentiality and integrity of sensitive contact notes on affected devices, potentially exposing personal or business information to unauthorized local actors. The issue is not remotely exploitable, but the low attack complexity and public proof-of-concept reference elevate the risk for organizations relying on this app in multi-user or BYOD environments.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce single-user device profiles on Android devices running the app, restrict installation of untrusted co-resident applications, and consider uninstalling Simple Contacts Pro versionCode 107 until a fix is available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-112928
GHSA-6cf3-9ppw-9w2c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB