Insecure direct object reference (IDOR) vulnerability in the MatchPoint API
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The facts do not describe a workaround. Until a fix is available, the facts give no specific steps to limit the affected API, so check the vendor's advisory for guidance.
- 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
The MatchPoint API has an insecure direct object reference flaw in how it handles the `actingasuser` HTTP header, which it does not check against the requester's authorization. An attacker can reach it remotely over the network without logging in or any user action, then manipulate sequential identifiers to view personal, banking, and financial data, private messages, and QR codes for physical access, or to change passwords, impersonate users, and transfer virtual balances on third-party accounts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Insecure direct object reference (IDOR) vulnerability in the MatchPoint API, which relies on the actingasuser HTTP header without verifying the requester's authorization for the specified user. Manipulation of sequential identifiers allows access to personal, banking, and financial data, private messages, and QR codes for physical access, as well as the ability to modify third-party accounts, change passwords, impersonate users, and transfer virtual balances.
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 facts do not describe a workaround. Until a fix is available, the facts give no specific steps to limit the affected API, so check the vendor's advisory for guidance.
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-111490
Is CVE-2026-111490 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?
The MatchPoint API accepts the actingasuser HTTP header without checking that the requester is authorized for the user it names. Because the identifiers are sequential, changing them can reach other users' personal, banking, and financial data, private messages, and QR codes for physical access. It can also modify third-party accounts, change passwords, impersonate users, and transfer virtual balances.Source: incibe.es
Am I affected, and how do I check?
The facts do not list any affected version ranges, so the exact affected versions are unknown. The issue concerns TPC Software's Matchpoint product and its MatchPoint API when it relies on the actingasuser header. To check, confirm the installed Matchpoint version and whether the MatchPoint API is in use.Source: incibe.es
How do I fix CVE-2026-111490?
The facts do not name a fixed version or an upgrade target. Check the vendor's advisory for a patched release before changing anything.Source: incibe.es
What if there's no patch?
The facts do not describe a workaround. Until a fix is available, the facts give no specific steps to limit the affected API, so check the vendor's advisory for guidance.Source: incibe.es