# CVE-2025-59424: LinkAce Vulnerable to Stored XSS on the Audit Page

> An authenticated attacker can inject malicious scripts via their username, which execute in administrators' browsers when viewing the audit log.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A: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:** 18 Sep 2025
- **Updated:** 18 Sep 2025
- **Also known as:** GHSA-289g-9gff-p4wh

## What is CVE-2025-59424?

CVE-2025-59424 is a high-severity cross-site scripting vulnerability in Kovah LinkAce, published on 18 Sep 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

LinkAce is a self-hosted archive to collect website links. Prior to 2.3.1, a Stored Cross-Site Scripting (XSS) vulnerability has been identified on the /system/audit page. The application fails to properly sanitize the username field before it is rendered in the audit log. An authenticated attacker can set a malicious JavaScript payload as their username. When an action performed by this user is recorded (e.g., generate or revoke an API token), the payload is stored in the database. The script is then executed in the browser of any user, particularly administrators, who views the /system/audit page. This vulnerability is fixed in 2.3.1.

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

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

It affects 1 product.


Products: Linkace Linkace.

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

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

## Is CVE-2025-59424 being exploited?

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

Public exploit code:

- LinkAce Stored Cross-Site Scripting (XSS) on the /system/audit page (github_poc): https://github.com/JOOJIII/CVE-2025-59424

## Other vulnerabilities in Kovah LinkAce

- [CVE-2026-27458](https://insights.sbomify.com/CVE-2026-27458/): LinkAce: Stored XSS in Atom Feed via CDATA Escape in List Description (high 8.7)
- [CVE-2025-62722](https://insights.sbomify.com/CVE-2025-62722/): LinkAce: Stored XSS Vulnerability in Link Title Field Through Social Media Sharing Feature (high 8.7)
- [CVE-2026-33953](https://insights.sbomify.com/CVE-2026-33953/): LinkAce's SSRF protection can be bypassed via internal hostname resolution in LinkAce (high 8.5)
- [CVE-2025-53838](https://insights.sbomify.com/CVE-2025-53838/): LinkAce has a Stored One Click XSS vulnerability (high 8.4)
- [CVE-2026-30953](https://insights.sbomify.com/CVE-2026-30953/): LinkAce affected by SSRF via link creation: NoPrivateIpRule not applied to LinkStoreRequest (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59424 is a high-severity cross-site scripting vulnerability in Kovah LinkAce, published on 18 Sep 2025. Any signed-in user can exploit it over the network, 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-59424 exists.

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

## Sources

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

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