# CVE-2025-53923: Emlog vulnerable to reflected Cross-site Scripting in admin panel

> Attackers can inject malicious scripts via the keyword parameter in the admin panel, potentially executing code in an administrator's browser.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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:** 16 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-vvx2-m94x-f54m

## What is CVE-2025-53923?

CVE-2025-53923 is a high-severity cross-site scripting vulnerability in Emlog Emlog, published on 16 Jul 2025. 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. A cross-site scripting (XSS) vulnerability in emlog up to and including pro-2.5.17 allows remote attackers to inject arbitrary web script or HTML via the keyword parameter. Due to lack of sanitization it is possible to inject HTML/JS code into keyword parameter. If one persuades an user into clicking into prepared link it is possible to execute any JS code in admin's browser. As of time of publication, no known patched versions exist.

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

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

It affects 1 product.


Products: Emlog Emlog.

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

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

## Is CVE-2025-53923 being exploited?

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

## Other vulnerabilities in Emlog Emlog

- [CVE-2025-29401](https://insights.sbomify.com/CVE-2025-29401/): File upload in n/a (critical 9.8)
- [CVE-2025-25783](https://insights.sbomify.com/CVE-2025-25783/): File upload in n/a (critical 9.8)
- [CVE-2023-44973](https://insights.sbomify.com/CVE-2023-44973/): File upload in n/a (critical 9.8)
- [CVE-2023-44974](https://insights.sbomify.com/CVE-2023-44974/): File upload in n/a (critical 9.8)
- [CVE-2023-43291](https://insights.sbomify.com/CVE-2023-43291/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53923 is a high-severity cross-site scripting vulnerability in Emlog Emlog, published on 16 Jul 2025. 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-2025-53923 exists.

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

## Sources

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

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