# CVE-2025-62618: ELOG file upload stored XSS

> Authenticated attackers can upload malicious HTML files to execute scripts in other users' browsers, potentially stealing credentials and session data.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Oct 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-9wg9-fwv6-cgcr

## What is CVE-2025-62618?

CVE-2025-62618 is a high-severity cross-site scripting vulnerability in ELOG, published on 31 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

ELOG allows an authenticated user to upload arbitrary HTML files. The HTML content is executed in the context of other users when they open the file. Because ELOG includes usernames and password hashes in certain HTTP requests, an attacker can obtain the target's credentials and replay them or crack the password hash offline. In ELOG 3.1.5-20251014 release, HTML files are rendered as plain text.

Weakness: CWE-836 (Use of Password Hash Instead of Password for Authentication), CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-62618?

It affects 1 product.


Products: Elog Project Elog.

## How do I fix CVE-2025-62618?

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

## Is CVE-2025-62618 being exploited?

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

## Other vulnerabilities in ELOG

- [CVE-2025-64348](https://insights.sbomify.com/CVE-2025-64348/): ELOG configuration file authorization bypass (critical 9.3)
- [CVE-2025-64349](https://insights.sbomify.com/CVE-2025-64349/): ELOG user profile missing authorization (high 8.7)
- [CVE-2019-3992](https://insights.sbomify.com/CVE-2019-3992/): Information disclosure in ELOG (high 7.5)
- [CVE-2019-3993](https://insights.sbomify.com/CVE-2019-3993/): Information disclosure in ELOG (high 7.5)
- [CVE-2019-3994](https://insights.sbomify.com/CVE-2019-3994/): Use after free in ELOG (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62618 and fix it if it is affected.

What it is: CVE-2025-62618 is a high-severity cross-site scripting vulnerability in ELOG, published on 31 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-62618 in the wild and no public exploit code.

Affected product: ELOG. 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-2025-62618/ (Markdown: https://insights.sbomify.com/CVE-2025-62618/index.md)
```

## Sources

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

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