Skip to main content
CVE-2025-62722VulnerabilityPublished

CVE-2025-62722: Kovah LinkAce · Cross-site Scripting

Affects Kovah LinkAceSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High : upgrade to 2.4.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade kovah/LinkAce to 2.4.0.

Affected software

ProductAffectedFixed in
GitHubkovah/LinkAcepkg:github/kovah/LinkAceOther threatsAffected
  • <2.4.0
Fixed in
  • 2.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade all LinkAce instances to version 2.4.0 or later immediately to apply the official fix. 2. Restrict authenticated user permissions to only trusted personnel to minimize the risk of malicious link creation. 3. Implement web application firewalls (WAFs) with rules to detect and block common XSS payloads targeting LinkAce endpoints. 4. Conduct regular audits of link titles and shared content for suspicious HTML or JavaScript code. 5. Educate users about the risks of clicking on shared links within LinkAce and encourage reporting of unusual behavior. 6. Where possible, isolate LinkAce instances within secure network segments to limit exposure. 7. Monitor logs for unusual activity related to link creation and access patterns. 8. Consider deploying Content Security Policy (CSP) headers to restrict script execution sources on LinkAce pages. These steps go beyond generic advice by focusing on access control, monitoring, and layered defenses specific to the application context.

Description

LinkAce is a self-hosted archive to collect website links. In versions 2.3.1 and below, the social media sharing functionality contains a Stored Cross-Site Scripting (XSS) vulnerability that allows any authenticated user to inject arbitrary JavaScript by creating a link with malicious HTML in the title field. When a user views the link details page and the shareable links are rendered, the malicious JavaScript executes in their browser. This vulnerability affects multiple sharing services and can be exploited to steal session cookies, perform actions on behalf of users, or deliver malware. This issue is fixed in version 2.4.0.

References

Community reviews

Loading reviews…