Skip to main content
VulnerabilityPublished

CVE-2026-111491: plain text · Credentials Are Stored

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-111491· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium.

Data as of 6 Nov 2026, 01:20 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (INCIBE)CVSS 4.06.9
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
TPC SoftwareMatchpointAffected
  • =Versions prior to latest one
Fixed in–

AI-suggested

Until a fix is available, users should avoid storing sensitive credentials on the device and consider device-level protections such as encryption and restricting physical access. Developers should update the app to securely store credentials using encrypted storage mechanisms.

Description

The MatchPoint Android app stores user credentials in plain text within an SQLite database and SharedPreferences. This insecure storage allows an attacker with local device access or access to backups to retrieve usernames and passwords, potentially leading to unauthorized account access on the platform.

References

Community reviews

Loading reviews…