dbcve.org
EmlogApplication

CVE-2026-22799

HIGH · 8.8 CVSS v3.1 Published 2026-01-12
Fix available
A fix is available. Upgrade to 2.6.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Emlog is an open source website building system. emlog v2.6.1 and earlier exposes a REST API endpoint (/index.php?rest-api=upload) for media file uploads. The endpoint fails to implement proper validation of file types, extensions, and content, allowing authenticated attackers (with a valid API key or admin session cookie) to upload arbitrary files (including malicious PHP scripts) to the server. An attacker can obtain the API key either by gaining administrator access to enable the REST API setting, or via information disclosure vulnerabilities in the application. Once uploaded, the malicious PHP file can be executed to gain remote code execution (RCE) on the target server, leading to full server compromise.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-434

The application accepts uploaded files without properly checking their type or content, so an attacker can upload something executable. If it lands where the server will run it, that is remote code execution. Remediating it means validating content rather than just the extension, storing uploads outside the web root, and never executing them.

General guidance for the unrestricted file upload class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EmlogApplication
Affected:< 2.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.1 or later
Fixed in 2.6.1
Vendor patch github.com →
Recommended fix High confidence

Emlog 2.6.2 or later (the release containing commit 429b02fda842254b9b9b39303e9161999c180560)

  1. 1. Verify current Emlog installation version by checking the version file or admin dashboard.
  2. 2. Navigate to the official Emlog GitHub repository at https://github.com/emlog/emlog.
  3. 3. Check the releases or tags section to identify the version containing the fix (version 2.6.2 or later, as the vulnerability affects versions < 2.6.1 and the patch commit 429b02fda842254b9b9b39303e9161999c180560 addresses the issue).
  4. 4. Download the fixed version release package.
  5. 5. Back up the entire Emlog installation directory and database before upgrading.
  6. 6. Extract the new version files to replace the existing installation, preserving any custom configurations or uploads directory.
  7. 7. Verify the /index.php?rest-api=upload endpoint now properly validates file types, extensions, and content before allowing uploads.
  8. 8. Confirm the REST API setting requires explicit admin enablement and API key authentication.
Caveat Review custom themes or plugins that may depend on the REST API behavior before upgrading, as file upload validation has been strengthened.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22799 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data