A static credential embedded in the mobile app has been reported to return the 'autorizado' token on the MatchPoint platform
Affects the MatchPoint sports facility management platform through its mobile app. No affected versions or fix are listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts list no workaround or fix. Until the vendor publishes one, the sources give no guidance on limiting exposure.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
A static credential embedded in the MatchPoint mobile app can be used to obtain an 'autorizado' token that grants access to the platform's API services. An attacker can reach this remotely, without logging in, and no user action is needed.
Read the original description
A static credential embedded in the mobile app has been reported to return the 'autorizado' token on the MatchPoint platform. The report states that this token grants unauthenticated access to API services.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.9/10CVSS 9.9
- No patch5/5No patch listed yet
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts list no workaround or fix. Until the vendor publishes one, the sources give no guidance on limiting exposure.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- TPC Software Matchpoint
Version range not reported
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111489
Is CVE-2026-111489 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A static credential embedded in the MatchPoint mobile app can be used to obtain a token that grants unauthenticated access to the platform's API services.Source: incibe.es
Am I affected, and how do I check?
The checked facts name the MatchPoint platform by TPC Software and tie the issue to its mobile app, but list no version ranges. Check the vendor's advisory or the app's version information to compare against any published range.Source: incibe.es
How do I fix CVE-2026-111489?
The checked facts give no fixed version or update, so no upgrade target can be stated. Check the vendor's channels for a later release or advisory.Source: incibe.es
What if there's no patch?
The checked facts list no workaround or fix. Until the vendor publishes one, the sources give no guidance on limiting exposure.Source: incibe.es