CVE-2026-73849: emlog allows unauthenticated reinstallation via `install.php?action=reinstall`.
Emlog is an open source website building system. In 2.6.26 and earlier, install.php accepts action=reinstall without authentication and deliberately skips the already-installed check because the guard runs only when $act != 'reinstall'. A remote attacker can submit hostname, dbuser, dbpasswd, dbname, dbprefix, username, password, and email values to cause file_put_contents('config.php', $config) to overwrite the configuration with attacker-controlled database settings and create a new administrator account. No fixed version is available as of this review.
Security readout for executives and security teams
Plain-English summary
An internet-accessible emlog site can be reinstalled by an unauthenticated attacker. This may replace its database configuration, create an attacker-controlled administrator, expose data, alter content, or disrupt service. Versions through 2.6.26 are affected, and the supplied sources report no fixed version.
Executive priority
Treat this as an immediate containment and investigation priority for exposed emlog systems. The flaw can enable full site takeover without credentials, while no fixed release is reported. Assign ownership today for inventory, access restriction, compromise review, and vendor-update monitoring.
Technical view
In emlog 2.6.26 and earlier, the installed-state guard excludes requests using the reinstall action. An unauthenticated remote request can supply database and administrator values, overwrite config.php, and create a new administrator account. The issue is classified as CWE-306 and scored CVSS 3.1 9.8.
Likely exposure
Highest risk applies to emlog 2.6.26 or earlier when install.php is reachable by untrusted networks. Exposure depends on deployed version, endpoint accessibility, and compensating access controls. The sources do not identify affected hosted services or deployment prevalence.
Exploitation context
The CVSS vector indicates network reachability, low complexity, no privileges, and no user interaction, with potentially complete confidentiality, integrity, and availability impact. The supplied record is not in KEV and provides no evidence of active exploitation; absence from KEV does not establish safety.
Researcher notes
The advisory describes an authentication omission caused by the reinstall exception in the installed-state check. Attacker-controlled configuration and administrator creation support the critical rating. Public evidence supplied here does not establish exploitation in the wild, affected code branches beyond 2.6.26, or an official patch.
Mitigation direction
Inventory emlog deployments and identify versions 2.6.26 or earlier.
Check the vendor advisory frequently for an official fixed version or supported remediation.
Until vendor guidance is available, prevent untrusted access to install.php using existing access controls.
Preserve configuration, database, account, and access-log evidence before incident-response changes.
Validation and detection
Confirm each deployed emlog version from authoritative package or application records.
Verify whether install.php is reachable from the internet or other untrusted networks.
Review config.php history for unexpected database-setting changes.
Audit administrator accounts for unauthorized additions or password changes.
Search web access logs for unexpected requests targeting the reinstall action.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Functionality
Missing Authentication for Critical Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.