/

CVE-2026-73849

Severity:

CRITICAL RISK

(9.8)

Unauthenticated Reinstallation (CWE-306) in Emlog CMS

CVE-2026-73849

Deferred

Vulnerability type

Category:

Missing Authentication for Critical Function

CWE:

CWE-306

Impact:

Unauthorized Administrative Access and Application Takeover

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Emlog permits an unauthenticated remote request to trigger its reinstallation workflow, even after the application has already been installed. An attacker may overwrite the application configuration with controlled database settings and create a new administrator account, potentially resulting in complete website takeover.

Affected context

The vulnerability occurs in Emlog deployments using the affected installation endpoint when the reinstallation action remains reachable without authentication. The already-installed safeguard is bypassed for that action, allowing attacker-supplied installation values to reach configuration-writing and administrator-creation logic.

Exploit preconditions

  • Attack surface: Publicly reachable Emlog installation endpoint
  • Required access: No authentication is required
  • Trigger point: Processing of the reinstallation action in install.php
  • Why exploitation is possible: The installed-state check is conditionally skipped, allowing unauthenticated input to control database configuration and administrator provisioning

Why this happens

The underlying defect is the absence of authentication and authorization for a security-sensitive reinstallation function. The application intentionally bypasses its already-installed guard when handling the reinstallation action, allowing an unauthenticated caller to invoke functionality that overwrites configuration and creates privileged accounts. This behavior maps to CWE-306: Missing Authentication for Critical Function.

Potential impact

  • An attacker may create a new administrator account
  • The application configuration may be overwritten with attacker-controlled database settings
  • Existing administrative access may be displaced or compromised
  • Website content and settings could be modified
  • Sensitive application or database data may be exposed
  • The server may become a staging point for further compromise

General mitigation guidance

Mitigation generally focuses on ensuring that installation and reinstallation functionality is unavailable after initial deployment unless it is explicitly authorized.

Common defensive patterns include:

  • Require strong authentication and authorization for all installation-state changes
  • Enforce the already-installed check for every installation-related action
  • Disable or remove installation endpoints after deployment
  • Apply server-side allowlisting for administrative setup operations
  • Protect configuration files from unauthorized writes
  • Run the application and database accounts with least privilege
  • Separate initial provisioning workflows from normal public web traffic

How teams detect issues like this

Organizations can look for this issue through:

  • Static analysis of installation handlers for unauthenticated state-changing actions
  • Code review signals such as conditional authentication checks based on user-controlled action values
  • Tests verifying that setup and reinstallation endpoints reject unauthenticated requests after initialization
  • Web-server logs showing unexpected requests to installation paths or reinstallation actions
  • File-integrity monitoring for unexpected changes to application configuration files
  • Policy enforcement that prevents production deployments from exposing setup functionality

Sources

SourceLink
github.comgithub.com/emlog/emlog/security/advisories/GHSA-v5qq-p8mp-3gxm

Frequently asked

questions

Yes. The affected installation endpoint may be reachable over the network, and the reinstallation action does not require an authenticated session.

No valid account is required when the vulnerable endpoint is publicly accessible. Network access to the Emlog installation handler is the key prerequisite.

Ensure that reinstallation is disabled after initial setup and that any exceptional setup operation requires authenticated, authorized administrative access.

Treat installation and configuration-changing functions as privileged operations, enforce authorization independently of action parameters, and test that production deployments do not expose setup workflows.

Find out what's already
exploitable in your codebase.