DataPer Access Control and Security Systems privilege escalation in authorization checks
- Exploited
- No known exploitation
- Fix
- Fixed in v14.15(2026/11)
- Who is exposed
- Not reported
Summary
A missing authorization check in Dataprom Informatics DataPer Access Control and Security Systems lets an attacker who has a low-privilege login gain higher privileges. The attack can be carried out remotely over the network without any user action.
Written by a model
Original description
Missing Authorization vulnerability in Dataprom Bilişim Teknolojileri LTD. ŞTİ. DataPer Access Control and Security Systems allows Privilege Escalation.
This issue affects DataPer Access Control and Security Systems: before v14.15(2026/11).
What to do
Upgrade to a fixed version: v14.15(2026/11).
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-101167 (Unauthenticated Privilege Escalation in Dataprom Informatics DataPer Access Control and Security Systems), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-101167 (entry last updated 2026-11-19):
Affected:
- Dataprom Bilişim Teknolojileri LTD. ŞTİ. DataPer Access Control and Security Systems: fixed in v14.15(2026/11)
Fixed versions: v14.15(2026/11).
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-101167 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-101167 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1577
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-101167
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-101167"}.Affected versions
- Dataprom Bilişim Teknolojileri LTD. ŞTİ. DataPer Access Control and Security Systemsfixed in v14.15(2026/11)
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-101167 |
| Record | NVD · CVE-2026-101167 |
| Other links 1 | |
| Link | siberguvenlik.gov.tr · guvenlik-bildirimleri/detay/tr-26-1577 |
Questions about CVE-2026-101167
Is CVE-2026-101167 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
Which versions are affected by CVE-2026-101167?
DataPer Access Control and Security Systems: before v14.15(2026/11).
Source: cve.now feed data
How do I fix CVE-2026-101167?
Upgrade to a fixed version: v14.15(2026/11).
Source: cve.now feed data
Related
- CVE-2026-129065WordPress WP Database Backup plugin <= 7.14 - Broken Access Control vulnerability
- CVE-2026-130055VidShop <= 1.10.0 - Missing Authorization to Unauthenticated Hidden Product Data Disclosure via '/vsfw/v1/products/{id}' REST API Endpoint
- CVE-2026-131709WordPress ShopEngine plugin <= 4.9.9 - Broken Access Control vulnerability
- CVE-2026-131796WordPress ShopMagic for Google Sheets plugin <= 2.1.9 - Broken Access Control vulnerability
- CVE-2026-131764WordPress SureCart plugin <= 4.13.0 - Broken Access Control vulnerability
- CVE-2026-131725WordPress Quiz And Survey Master plugin <= 11.3.1 - Broken Access Control vulnerability
No corrections so far. Something wrong on this page? Report an error.