Investory Toy Planet Trouble App up to 1.5.5 on Android app.investory.toyfactory google-services-desktop.json current_key hard-coded key

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.0$0-$5k1.89

Summaryinfo

A vulnerability was found in Investory Toy Planet Trouble App up to 1.5.5 on Android. It has been rated as problematic. The affected element is an unknown function of the file assets/google-services-desktop.json of the component app.investory.toyfactory. This manipulation of the argument current_key causes hard-coded key. This vulnerability is registered as CVE-2026-5471. The attack needs to be launched locally. Furthermore, an exploit is available.

Detailsinfo

A vulnerability was found in Investory Toy Planet Trouble App up to 1.5.5 on Android. It has been declared as problematic. Affected by this vulnerability is an unknown function of the file assets/google-services-desktop.json of the component app.investory.toyfactory. The manipulation of the argument current_key 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.

It is possible to read the advisory at notion.so. This vulnerability is known as CVE-2026-5471. The exploitation appears to be easy. Attacking locally is a requirement. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.

It is possible to download the exploit at notion.so. It is declared as proof-of-concept. By approaching the search of inurl:assets/google-services-desktop.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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Hard-coded key
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

04/03/2026 Advisory disclosed
04/03/2026 +0 days VulDB entry created
04/03/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: notion.so
Status: Not defined

CVE: CVE-2026-5471 (🔒)
GCVE (CVE): GCVE-0-2026-5471
GCVE (VulDB): GCVE-100-355075
scip Labs: https://www.scip.ch/en/?labs.20130704

Entryinfo

Created: 04/03/2026 09:42
Changes: 04/03/2026 09:42 (58)
Complete: 🔍
Submitter: fxizenta
Cache ID: 216:859:103

Submitinfo

Accepted

  • Submit #781784: INVESTORY Investory(app.investory.toyfactory) 1.5.5 Firebase API Key Exposure (by fxizenta)

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!