# CVE-2026-46686: Emlog Reflected Cross-Site Scripting

> Attackers can inject malicious scripts into the admin user search interface, potentially compromising administrator sessions in Emlog.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA: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:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-3h87-c3m2-jpj9

## What is CVE-2026-46686?

CVE-2026-46686 is a high-severity cross-site scripting vulnerability in emlog, published on 16 Jul 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.13 and earlier, the admin backend user search module's keyword parameter from admin/user.php is processed with addslashes but not HTML-escaped before being rendered into the value attribute in admin/views/user.php, allowing reflected cross-site scripting in an administrator's backend session. No fixed version is currently identified.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-46686 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46686 is a high-severity cross-site scripting vulnerability in emlog, published on 16 Jul 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-46686 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-46686/ (Markdown: https://insights.sbomify.com/CVE-2026-46686/index.md)
```

## Sources

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

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