Emlog
CVE-2026-34228
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious upgrade link with SQL/ZIP URLs
-
DeliveryTrick administrator into clicking link
-
ExploitServer downloads and executes remote SQL
-
ExecutionExtract ZIP into web root
-
ImpactAchieve arbitrary code execution
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Attacker must trick an authenticated Emlog administrator (versions before 2.6.8) into visiting a malicious link containing crafted GET parameters pointing to remote SQL and ZIP URLs. The backend upgrade interface lacks CSRF token validation, enabling arbitrary SQL execution and file writes to web root. |
| Impact | The CVSS v4.0 score of 8.7 (High severity) reflects significant real-world risk due to the combination of network-based attack vector (AV:N), low attack complexity (AC:L), and no required privileges (PR:N) or user interaction (UI:N) from the attacker's perspective. However, the attack does require social engineering to trick an authenticated administrator, which introduces practical friction not fully captured in the base score. The vulnerability enables high integrity impact (VI:H) through arbitrary SQL execution and file writes, creating pathways to full system compromise, web shell deployment, and data manipulation. With publicly available exploit code not identified and no CISA KEV listing, immediate widespread exploitation appears limited. The SSVC decision framework would classify this as exploitation status 'POC' (proof-of-concept exists via detailed advisory), automatable 'No' (requires social engineering), and technical impact 'Total' (arbitrary code execution possible). The primary risk lies in targeted attacks against Emlog installations where administrators can be socially engineered, particularly in environments lacking defense-in-depth controls like Content Security Policy or strict referrer validation. Organizations should prioritize patching if Emlog is internet-facing or administrators operate from potentially compromised networks. |
| Exploit ScenarioDerived | An attacker crafts a malicious webpage containing hidden image tags or JavaScript that generates GET requests to the victim's Emlog backend upgrade interface, embedding URLs pointing to attacker-controlled SQL and ZIP files. When an authenticated Emlog administrator visits this malicious page while logged into their CMS dashboard, their browser automatically sends the requests with valid session cookies. The Emlog server downloads the attacker's SQL file and executes it against the database, potentially creating administrative accounts or exfiltrating credentials. Subsequently, the server downloads and extracts the malicious ZIP archive into the web root, deploying a PHP web shell that grants the attacker persistent remote code execution. The entire attack requires only a single click on a phishing link, with no interaction warnings presented to the victim administrator. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 03, 2026
Cross-Site Request Forgery (CSRF) in Emlog CMS versions prior to 2.6.8 enables remote attackers to execute arbitrary SQL commands and write arbitrary files to the web root without authentication. The vulnerability exploits an unprotected backend upgrade interface that accepts remote SQL and ZIP URLs via GET parameters, requiring only that an authenticated administrator visit a malicious link. EPSS data not available; no public exploit identified at time of analysis, though exploitation complexity is low given the CSRF nature and network attack vector.
RemediationAI
Vendor-released patch: Emlog version 2.6.8 resolves this vulnerability by implementing CSRF token validation in the backend upgrade interface. Organizations running affected versions should immediately upgrade to Emlog 2.6.8 or later, available through the official GitHub repository. The specific remediation commit implementing CSRF protection is documented at https://github.com/emlog/emlog/commit/4c3b8f3486e2c9caafee38a5eedb3cd16f8c8d6f. As an interim mitigation for environments unable to upgrade immediately, administrators should restrict access to the backend upgrade interface through IP allowlisting, implement strict referrer validation at the web server level, or disable the upgrade functionality entirely if not actively used. Additionally, educating administrators about CSRF attack vectors and implementing browser-based protections like SameSite cookie attributes can reduce exploitation risk. Review web server access logs for suspicious requests to upgrade endpoints containing external URL parameters as potential indicators of exploitation attempts.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Emlog is an open-source PHP-based content management system. The vulnerability resides in the backend upgrade mechanism, specifically an interface that processes GET parameters containing URLs to remote SQL files and ZIP archives. The affected product (cpe:2.3:a:emlog:emlog) implements this upgrade workflow without CSRF token validation, classified as CWE-352 (Cross-Site Request Forgery). The attack chain involves two stages: first, the server downloads and executes a remote SQL file directly against the database; second, it downloads a ZIP archive and extracts contents into the web root without path validation or integrity checks. This design flaw allows state-changing operations via simple HTTP GET requests, violating the principle that GET requests should be idempotent and safe. The lack of CSRF protection means the victim's authenticated session can be hijacked through social engineering, with the browser automatically including session cookies when requesting the malicious URL.
Know when Emlog 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
DescriptionCVE.org
Emlog is an open source website building system. Prior to version 2.6.8, the backend upgrade interface accepts remote SQL and ZIP URLs via GET parameters. The server first downloads and executes the SQL file, then downloads the ZIP file and extracts it directly into the web root directory. This process does not validate a CSRF token. Therefore, an attacker only needs to trick an authenticated administrator into visiting a malicious link to achieve arbitrary SQL execution and arbitrary file write. This issue has been patched in version 2.6.8.
Executive ViewAI
Emlog CMS versions before 2.6.8 contain a critical CSRF vulnerability that allows attackers to trick authenticated administrators into executing arbitrary SQL commands and uploading malicious files to the web server, potentially leading to complete system compromise. Organizations running affected Emlog instances face immediate risk of data breach, website defacement, and lateral movement into backend systems. This vulnerability requires no attacker authentication but relies on social engineering to compromise administrative users.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable or restrict network access to the Emlog backend upgrade interface using firewall rules or web application firewall (WAF) blocking; (2) Implement strict SameSite=Strict cookie policies on session tokens; (3) Enforce additional authentication factors (IP whitelist, VPN requirement) for administrative access; (4) Deploy CSRF token validation at the WAF or reverse proxy level; (5) Monitor access logs for suspicious GET requests to upgrade endpoints containing 'sql' or 'zip' parameters.
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
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
Affected Products (CPE)CVE.org
An arbitrary file upload vulnerability in the component /views/plugin.php of emlog pro v2.5.7 allows attackers to execut
An arbitrary file upload vulnerability in the component /admin/plugin.php of Emlog Pro v2.2.0 allows attackers to execut
An arbitrary file upload vulnerability in the component /content/templates/ of Emlog Pro v2.2.0 allows attackers to exec
Deserialization of Untrusted Data in emlog pro v.2.1.15 and earlier allows a remote attacker to execute arbitrary code v
A Remote Code Execution (RCE) vulnerability exists in emlog 5.3.1 via content/plugins. Rated critical severity (CVSS 9.8
emlog v5.3.1 and emlog v6.0.0 have a Remote Code Execution vulnerability due to upload of database backup file in admin/
emlog through 6.0.0beta has an arbitrary file deletion vulnerability via an admin/data.php?action=dell_all_bak request w
Emlog Pro 2.5.20 has an arbitrary file deletion vulnerability. This vulnerability stems from the admin/template.php comp
Emlog 2.5.23 is vulnerable to CSRF in article creation, which chains with stored XSS to achieve account takeover. An att
Remote code execution in Emlog v2.6.1 and earlier allows authenticated attackers to upload arbitrary files through an in
Cross-site request forgery in Emlog Pro 2.5.19 and earlier can lead to account takeover of a privileged administrator be
An issue was discovered in emlog 6.0.0stable. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB