# CVE-2026-73848: Emlog: Stored XSS via Tag Name in Article Editor

> Attackers can execute arbitrary JavaScript in the article editor via malicious tag names, potentially compromising user sessions.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/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:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-fv6h-wr92-v4pj

## What is CVE-2026-73848?

CVE-2026-73848 is a medium-severity cross-site scripting vulnerability in emlog, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Emlog is an open source website building system. In versions 2.6.29 and prior, tag names in emlog are not HTML-encoded when rendered in the article editor. An attacker can create a tag containing ');alert(document.domain);//. The addslashes() function does not escape HTML entities, so ' is stored as-is. When the browser renders the page, it decodes ' back to a literal single quote before evaluating the JavaScript, breaking out of the string and executing arbitrary code. At time of publication, there are no publicly known patches.

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

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


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

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

## Is CVE-2026-73848 being exploited?

There is no known exploitation of CVE-2026-73848 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73848 is a medium-severity cross-site scripting vulnerability in emlog, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73848 in the wild and no public exploit code.

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-73848/ (Markdown: https://insights.sbomify.com/CVE-2026-73848/index.md)
```

## Sources

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

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