Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-7189 – Unauthenticated Sensitive Data Disclosure and ACL Bypass – Proliz OBS before v3.6.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-7189 is a high-severity vulnerability (CVSS 8.2) affecting Proliz Software Ltd. Co.’s OBS — a web-based Student Affairs Information System (Öğrenci Bilgi Sistemi) deployed across Turkish universities. The flaw involves the insertion of sensitive information into transmitted data (CWE-201), enabling unauthenticated remote attackers to access functionality not properly constrained by access control lists (ACLs). All versions of Proliz OBS prior to v3.6.0 are affected.

Technical details

  • Root cause: The application inserts sensitive information into data sent over the network (CWE-201). This exposed data can be leveraged by an attacker to bypass access controls and reach functionality that should be restricted.
  • Trigger conditions: Exploitable remotely with no authentication and no user interaction required. The OBS platform is internet-facing by design — students, faculty, and administrators access it via public URLs — making all unpatched instances directly reachable.
  • Attack vector: Network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: High confidentiality impact — sensitive information is exposed; low integrity impact — an attacker can reach and interact with ACL-constrained functionality (CAPEC-1). No availability impact.

Affected software

  • Proliz OBS (Student Affairs Information System) — all versions prior to v3.6.0

Severity

  • CVSS v3.1 Base Score: 8.2 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Proliz OBS to v3.6.0 or later, which contains the vendor-provided fix per the Turkish Cyber Security Authority advisory (TR-26-0571).
  • If immediate patching is not feasible: Restrict network access to OBS-hosted endpoints to trusted institutional IP ranges and monitor access logs for anomalous unauthenticated requests targeting protected application paths.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge