What is the CVSS score of EUVD-2026-42988?

EUVD-2026-42988 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of TeraMIS are affected by EUVD-2026-42988?

Teracity TeraMIS (versions through April 30, 2026 build) contains an authorization bypass vulnerability enabling any authenticated user to access and modify data and functions belonging to other…

How to fix or mitigate EUVD-2026-42988?

Within 24 hours: Identify all deployed TeraMIS instances and document affected versions (V03.26.01.14 through 30.04.2026 build); assess which systems contain regulated or highly sensitive data. Within 7 days: Restrict TeraMIS access to administrative users only if operationally feasible; enable real-time monitoring for unauthorized cross-user data access; establish contact with Teracity to obtain patch release timeline. Within 30 days: Deploy all available compensating controls; develop upgrade plan for patched version upon release; conduct access log review to identify potential exploitation.

TeraMIS EUVD-2026-42988

| CVE-2026-6212 HIGH

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-07-10 TR-CERT

GHSA-g6gj-wmj4-88pr

Authentication Bypass Teramis

8.8

CVSS 3.1 · Vendor: TR-CERT

Severity by source

Vendor (TR-CERT) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

8.3 HIGH

Remote low-complexity IDOR needing a low-privilege account (AV:N/AC:L/PR:L); high confidentiality and integrity from cross-account read/write, but availability only Low since an authz bypass rarely destroys the whole system.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (TR-CERT).

CVSS VectorVendor: TR-CERT

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 10, 2026 - 19:24 vuln.today

DescriptionCVE.org

Authorization bypass through User-Controlled key vulnerability in Teracity Software Technologies Inc. TeraMIS allows Privilege Abuse.

This issue affects TeraMIS: from V03.26.01.14 through 30.04.2026.

AnalysisAI

Authorization bypass in Teracity TeraMIS (versions V03.26.01.14 through the 30.04.2026 build) lets an authenticated low-privilege user tamper with a user-controlled object key to reach records and functions belonging to other users or higher-privilege roles (CWE-639 IDOR). The CVSS vector (AV:N/AC:L/PR:L/UI:N) confirms remote, low-complexity exploitation by any account holder, yielding high confidentiality and integrity impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; EPSS and POC data were not provided.

Technical ContextAI

TeraMIS is a management information system (MIS) web application from the Turkish vendor Teracity Software Technologies Inc., flagged in this advisory by TR-CERT (USOM). The root cause is CWE-639, Authorization Bypass Through a User-Controlled Key - a classic Insecure Direct Object Reference (IDOR). The application uses a client-supplied identifier (such as a record ID, account ID, or request parameter) to select the target object but fails to verify that the authenticated session is actually authorized for that object. Because the key is user-controlled and the server trusts it, an attacker can substitute another user's or role's identifier and the application returns or modifies data it should have denied. The single CPE, cpe:2.3:a:teracity_software_technologies_inc.:teramis:*:*:*:*:*:*:*:*, is a wildcard covering all TeraMIS builds and does not itself bound the affected range.

RemediationAI

No vendor-released patch version is identified in the available data, so a specific fixed build cannot be cited; consult the TR-CERT bulletin at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0528 and contact Teracity for a corrected release beyond the 30.04.2026 build. The definitive fix is code-level and must come from the vendor: enforce server-side authorization on every object reference so the server verifies the session is entitled to the requested key rather than trusting the client-supplied ID. As compensating controls, restrict TeraMIS to trusted networks or VPN to shrink the pool of low-privilege attackers, tighten role assignment so accounts hold only minimum privileges, and enable detailed access logging with alerting on anomalous ID enumeration or cross-account access (trade-off: increased log volume and review overhead). A WAF rule to detect sequential or out-of-range identifier access can help, accepting that pattern matching cannot reliably separate legitimate from malicious object references and may generate false positives.