GRID Organiser App up to 1.0.5 on Android co.gridapp.organiser file res/raw/app.json SegmentWriteKey hard-coded key
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 2.28- |
Summary
A vulnerability, which was classified as problematic, was found in GRID Organiser App up to 1.0.5 on Android. The affected element is an unknown function of the file file res/raw/app.json of the component co.gridapp.organiser. Executing a manipulation of the argument SegmentWriteKey can lead to hard-coded key. This vulnerability is tracked as CVE-2026-5454. The attack is restricted to local execution. Moreover, an exploit is present.
Details
A vulnerability classified as problematic was found in GRID Organiser App up to 1.0.5 on Android. This vulnerability affects some unknown functionality of the file file res/raw/app.json of the component co.gridapp.organiser. The manipulation of the argument SegmentWriteKey with an unknown input leads to a hard-coded key vulnerability. The CWE definition for the vulnerability is CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. As an impact it is known to affect confidentiality.
The advisory is available at notion.so. This vulnerability was named CVE-2026-5454. The exploitation appears to be easy. Local access is required to approach this attack. Technical details and also a public exploit are known. This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project.
It is possible to download the exploit at notion.so. It is declared as proof-of-concept. By approaching the search of inurl:file res/raw/app.json it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-18599). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/02/2026 VulDB entry created04/03/2026 Advisory disclosed
04/03/2026 VulDB entry last update
Sources
Advisory: notion.soStatus: Not defined
CVE: CVE-2026-5454 (🔒)
GCVE (CVE): GCVE-0-2026-5454
GCVE (VulDB): GCVE-100-355042
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 04/03/2026 00:19Updated: 04/03/2026 12:18
Changes: 04/03/2026 00:19 (58), 04/03/2026 12:18 (1)
Complete: 🔍
Submitter: fxizenta
Cache ID: 216:461:103
Submit
Accepted
- Submit #781759: GRID GmbH GRID ORGANISER(co.gridapp.organiser) 1.0.5 Segment Write Key Exposure (by fxizenta)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.