# CVE-2026-16307: IDOR in Netiket Information Technologies' EdoWEB

Status: published. Published: 2026-10-27. Updated: 2026-11-04.

Authorization bypass through User-Controlled key vulnerability in Netiket Information Technologies EdoWEB allows Accessing Functionality Not Properly Constrained by ACLs.

This issue affects EdoWEB: before 780-g7.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Netiket Information Technologies / EdoWEB: ≥ 0; < 780-g7 (affected, semver). Source: CNA: TR-CERT

## Severity and prioritization

- CVSS 3.1: 4.3 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N; source: CNA: TR-CERT

- CISA KEV: No listing in collected sources

- EPSS: 0.19% as of 2026-11-04; percentile 8.86%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-639

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1409 (CNA: TR-CERT; government-resource)

## Provenance

- CNA: TR-CERT: https://www.cve.org/CVERecord?id=CVE-2026-16307; retrieved 2026-11-04; source updated 2026-11-04

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-16307; retrieved 2026-11-04; source updated Not reported

Revision: 74b121c182d3515c7d436e54aee9c7aa3b378ee60d8d22ba88d35abde881b550

Canonical: https://y2.dev/cve/CVE-2026-16307

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.