Skip to main content

Wiki CVE-2026-32736

| EUVDEUVD-2026-12981 MEDIUM
Missing Authorization (CWE-862)
2026-03-18 GitHub_M
4.3
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS v3.1 vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) indicates low-to-moderate risk with a score of 4.3. The attack vector is network-based, attack complexity is low, requires only low-privilege authentication (PR:L), involves no user interaction, and impacts only confidentiality (C:L) within the system's scope. However, the real-world risk is elevated by the nature of exposed data: mod authors' PII (names and email addresses) are exposed to an unlimited number of authenticated users who can enumerate mod pages. While no active exploitation or POC is explicitly documented in the provided intelligence, the triviality of the attack (simple authenticated HTTP requests to predictable URLs) makes it highly automatable. From an SSVC perspective, this represents a situation where exploitation is straightforward and the technical impact (exposure of PII) is concrete. The availability of a security patch (version 1.0.0) further indicates vendor awareness and resolution. Organizations hosting user-generated content or managing author registries should prioritize patching, particularly given potential GDPR/privacy law implications depending on user jurisdiction.

Exploit ScenarioDerived

An attacker creates a free account on the Hytale Modding Wiki and begins systematically visiting mod pages (e.g., /mod/slug-name-1, /mod/slug-name-2, etc.) or iterating through known mod identifiers. Due to the IDOR flaw, each page returns the mod author's full name and email address without authorization checks. The attacker harvests this PII for all public mods, enabling phishing attacks, spam campaigns, or identity-based social engineering against mod creators. The attack requires only network access and a valid account, no special tools, and can be fully automated to compromise the privacy of hundreds of mod authors.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 18, 2026

An Insecure Direct Object Reference (IDOR) vulnerability in the Hytale Modding Wiki prior to version 1.0.0 allows any authenticated user to access and view mod authors' personal information, including full names and email addresses, by navigating directly to mod pages using their slugs. The vulnerability requires only low-privilege authentication (account creation) and no user interaction, making it trivially exploitable. While the CVSS score is moderate at 4.3, the exposure of personally identifiable information (PII) represents a direct privacy harm to affected mod authors.

RemediationAI

Immediately upgrade the Hytale Modding Wiki to version 1.0.0 or later, which includes the authorization fix committed at https://github.com/HytaleModding/wiki/commit/4a96b3f9bce9a9d34030c39a8d6e4c6b6183f13d. Until patching is completed, temporary mitigation may include restricting wiki access to a smaller set of authenticated users, implementing rate limiting on mod page requests to detect enumeration attempts, or reviewing access logs to identify unauthorized access to author information. Verify that the patch correctly implements per-resource authorization checks before granting access to mod metadata.

Affected VersionsENISA

wiki < 1.0.0

Affected Packages

euvd wiki fix: 1.0.0

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 vulnerability stems from a failure to properly validate authorization on object access, classified under CWE-862 (Missing Authorization). The Hytale Modding Wiki application (CPE: cpe:2.3:a:hytalemodding:wiki:*:*:*:*:*:*:*:*) appears to implement authentication checks at the account/session level but does not enforce sufficient authorization controls on individual mod resources. When an authenticated user requests a mod page via its slug (a human-readable URL identifier), the backend returns sensitive author metadata without verifying whether the requesting user has permission to view that data. This is a common IDOR pattern where object identifiers are predictable (standard slug formats) and access controls are either absent or bypassable through direct enumeration.

Know when Wiki 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

GitHub Advisory PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
1.0.0
CVE Published
Mar 18, 2026 - 22:06 nvd
MEDIUM 4.3

DescriptionGitHub Advisory

The Hytale Modding Wiki is a free service for Hytale mods to host their documentation & wikis. An Insecure Direct Object Reference (IDOR) vulnerability in versions of the wiki prior to 1.0.0 exposes mod authors' personal information - including full names and email addresses - to any authenticated user who visits a mod page. Any user who creates an account can access sensitive author details by simply navigating to a mod's page via its slug. Version 1.0.0 fixes the issue.

Executive ViewAI

Why It Matters

Organizations using versions of the wiki should be aware of moderate risk from CVE-2026-32736, a missing authorization vulnerability rated CVSS 4.3. Attackers could gain access beyond their authorized level. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.0%
Top 93% exploitable
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Low

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Related Vulnerabilities in OpenEMR Access Control Flaws

View all 2

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy