Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious XML document with XXE payload
-
DeliveryDeliver document to UYAP user via phishing or shared storage
-
ExploitUser opens document in vulnerable editor
-
ExecutionParser resolves external entity reference
-
PersistSensitive local file contents returned to document
-
ImpactAttacker exfiltrates data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A02:2025 - Security Misconfiguration
ASVS 5.0
V13 - Configuration XML external entity prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the victim user actively opens a specially crafted XML-based document within the vulnerable UYAP Document Editor (versions 4.5.17 to before 5.4.17). The attack is local in vector (AV:L), meaning the malicious document must already be present on or delivered to the local file system - remote unauthenticated exploitation over a network is not applicable. No elevated privileges are required to open the document, but user interaction (opening the file) is mandatory. Exploitation is limited to users running affected versions of UYAP Document Editor, which is a government-specific judicial application predominantly deployed within Turkey's Ministry of Justice ecosystem. Key limiting factors: (1) the attacker must successfully deliver the crafted document to the target user, (2) the user must actively open it, and (3) the file system paths readable via XXE are constrained by the OS-level permissions of the running user account. |
| Impact | The CVSS 3.1 base score of 6.3 (Medium) is consistent with the vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N. The local attack vector (AV:L) limits exposure significantly - an attacker cannot exploit this remotely without first delivering a malicious document to the target machine. User interaction (UI:R) adds a further friction point: exploitation depends on a victim actively opening the crafted file. However, confidentiality impact is rated High with scope change, meaning a successful attack can read sensitive system files (e.g., credentials, configuration, private documents). No EPSS score data was provided, making probabilistic exploitation assessment unavailable. The vulnerability is not listed in CISA KEV and no public proof-of-concept exploit has been identified. Given the niche government-specific deployment context of UYAP Document Editor, realistic risk is bounded to organizations within Turkey's judicial and legal system. The primary real-world threat is a targeted spear-phishing or insider document delivery scenario, not opportunistic mass exploitation. |
| Exploit ScenarioDerived | An attacker crafts a malicious document embedding an XXE payload that references a sensitive local file (e.g., a credentials store or private configuration file). The document is delivered to a UYAP Document Editor user via email or shared storage within a judicial or legal organization. When the user opens the file, the unpatched editor resolves the external entity, and the contents of the targeted file are disclosed to the attacker. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 12, 2026
XML External Entity (XXE) injection in UYAP Document Editor versions 4.5.17 through 5.4.17 allows a local attacker to exfiltrate sensitive file system contents by tricking a user into opening a specially crafted document. The vulnerability enables serialized data external linking via uncontrolled XML external entity resolution, resulting in high confidentiality impact with scope change to the underlying operating system. Reported by TR-CERT; no public exploit code or CISA KEV listing identified at time of analysis.
RemediationAI
Upgrade UYAP Document Editor to version 5.4.17 or later, which resolves the improper XML external entity handling per the TR-CERT advisory at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0818. If immediate patching is not feasible, a compensating control is to restrict user-level access so that only documents from trusted, verified sources are opened in the editor - this reduces the document delivery attack surface but does not eliminate the underlying parser flaw. Organizations should also consider placing the editor in a sandboxed or reduced-privilege environment to limit the file system paths accessible via XXE resolution, accepting the trade-off that some legitimate document features relying on external references may break. Do not open unsolicited or unverified XML-based documents in UYAP Document Editor until the patch is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected product, identified by CPE cpe:2.3:a:ministry_of_justice:uyap_document_editor:*:*:*:*:*:*:*:*, is a document editing application developed by Turkey's Ministry of Justice for use in judicial and legal workflows. CWE-611 (Improper Restriction of XML External Entity Reference) describes the root cause: the XML parser in the editor fails to disable or restrict the resolution of external entity references embedded within document markup. When a document declares an external entity pointing to a local file path or network resource, the parser fetches and inlines that resource's contents. The CVSS scope change (S:C) reflects the fact that successful exploitation crosses the application boundary, reaching OS-level file system resources beyond the document editor's own data store.
Know when Uyap Document Editor gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
File-based delivery requires local access (AV:L) and user action (UI:R); XXE reads OS files crossing scope (S:C/C:H) with no write or availability impact.
Primary rating from Vendor (TR-CERT).
CVSS VectorVendor: TR-CERT
Lifecycle Timeline
1DescriptionCVE.org
Improper restriction of XML external entity reference vulnerability in Ministry of Justice UYAP Document Editor allows Serialized Data External Linking.
This issue affects UYAP Document Editor: from 4.5.17 before 5.4.17.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
XML External Entity (XXE) attacks exploit XML parsers that process Document Type Definitions (DTDs) without proper restrictions.
More in Uyap Document Editor
View allUnsafe deserialization in the UYAP Document Editor before version 5.4.20 allows an attacker to inject objects into the a
OS command injection in the Ministry of Justice General Directorate of Information Technology's UYAP Document Editor bef
EUVD-2026-57212
GHSA-vw7v-jmvx-4grc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB