# CVE-2026-73847: Cross-site request forgery in emlog

> Missing CSRF protection in Emlog's AI Assistant allows attackers to execute arbitrary SQL queries, leading to full database compromise and admin account takeover.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-v6wr-4x55-7qp5

## What is CVE-2026-73847?

CVE-2026-73847 is a medium-severity vulnerability in emlog, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Emlog is an open source website building system. In 2.6.26 and earlier, missing CSRF protection on the AI Assistant execute_tool action in admin/ai.php lets a remote unauthenticated attacker submit a forged cross-site request from an attacker-controlled page to a recently logged-in administrator. The authentication cookie set in include/lib/loginauth.php has no explicit SameSite attribute, enabling Chrome's temporary Lax+POST grace window. The query_database case passes attacker-controlled sql and confirm_code values to Ai::queryDatabase in include/service/ai.php; read queries need no confirmation, write queries accept the public confirm string, only the blog table is write-protected, and aliasing password as pwd_hash bypasses output redaction. A successful request can read every database table and write every table except blog, including changing the user table to take over an administrator account. No fixed version is available as of this review.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-352 (Cross-Site Request Forgery), CWE-1275 (Sensitive Cookie with Improper SameSite Attribute)

## Which versions are affected by CVE-2026-73847?


## How do I fix CVE-2026-73847?

No fix has been published for CVE-2026-73847 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73847 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73847 exists.

Public exploit code:

- PoC for CVE-2026-73847 - emlog AI Assistant CSRF to SQL execution to admin takeover (CVSS 6.8) (github_poc): https://github.com/squeeze440/CVE-2026-73847-emlog-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73847 and fix it if it is affected.

What it is: CVE-2026-73847 is a medium-severity vulnerability in emlog, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73847 exists.

Affected product: emlog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73847/ (Markdown: https://insights.sbomify.com/CVE-2026-73847/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73847
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73847
- OSV: https://osv.dev/vulnerability/CVE-2026-73847

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73847/
Summaries are generated and may contain mistakes; the official description above is the record.