Skip to main content
VulnerabilityPublished

CVE-2025-52360: Koha · Cross-site Scripting

Affects KohaSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubkoha/Kohapkg:github/koha/KohaOther threatsAffected
  • =24.05
Fixed in–

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

AI-suggested

To mitigate this vulnerability, European organizations using Koha LMS should immediately implement input validation and output encoding on the OPAC search feature and the search history interface to ensure that any user-supplied input is properly sanitized before being rendered in the browser. Specifically, all special characters in search inputs should be escaped or removed to prevent script injection. Organizations should monitor official Koha security advisories for patches addressing this issue and apply updates promptly once available. In the interim, administrators can consider disabling or restricting access to the search history feature to reduce exposure. Employing Content Security Policy (CSP) headers can help limit the impact of any injected scripts by restricting the sources from which scripts can be executed. Additionally, user education about the risks of interacting with suspicious search history entries and regular security audits of the Koha installation can help detect and prevent exploitation. Logging and monitoring for unusual activity related to the search feature may also aid in early detection of attempted attacks.

Description

A Cross-Site Scripting (XSS) vulnerability exists in the OPAC search feature of Koha Library Management System v24.05. Unsanitized input entered in the search field is reflected in the search history interface, leading to the execution of arbitrary JavaScript in the browser context when the user interacts with the interface.

References

Community reviews

Loading reviews…