VulnerabilityPublished 31 Aug 2025Updated 2 Sep 2025

CVE-2025-9747: Koillection · Cross-Site Request Forgery

Affects KoillectionSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Koillection	Affected 1.6.0 – 1.6.18 19 affected builds	Fixed in–

AI-suggested

Immediate upgrade to Koillection version 1.7.0 or later, which includes the patched CSRF protection mechanism using stateless tokens.
Implement additional CSRF defenses such as SameSite cookie attributes (Strict or Lax) to reduce the risk of CSRF attacks via cross-site requests.
Conduct user training and awareness campaigns to educate users about the risks of clicking unsolicited links or visiting untrusted websites while authenticated to critical applications.
Employ web application firewalls (WAFs) with rules designed to detect and block suspicious CSRF attack patterns targeting Koillection endpoints.
Review and minimize the use of persistent authentication cookies and ensure secure cookie flags (HttpOnly, Secure) are set to reduce session hijacking risks that could compound CSRF attacks.
Monitor application logs for unusual or unauthorized actions that could indicate attempted or successful exploitation.
For organizations unable to immediately upgrade, consider implementing temporary mitigations such as CSRF token validation at the application level or restricting access to the vulnerable application to trusted networks until patched.

Description

A vulnerability has been found in Koillection up to 1.6.18. Affected is an unknown function of the file assets/controllers/csrf_protection_controller.js. Such manipulation leads to cross-site request forgery. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.7.0 is able to address this issue. The name of the patch is 9ab8562d3f1e953da93fed63f9ee802c7ea26a9a. It is suggested to upgrade the affected component. The vendor explains: "I ended up switching to a newer CSRF handling using stateless token."

Impact

For European organizations, the CSRF vulnerability in Koillection could lead to unauthorized actions being performed on behalf of legitimate users, potentially resulting in data manipulation, unauthorized transactions, or configuration changes depending on the application's functionality. While the confidentiality impact is minimal, the integrity of data and operations could be compromised, leading to operational disruptions or reputational damage. Organizations in sectors with strict data protection regulations, such as finance, healthcare, or government, could face compliance issues if such unauthorized actions result in data breaches or service disruptions. The medium severity rating suggests a moderate risk, but the ease of exploitation via social engineering (e.g., phishing emails with malicious links) increases the threat level. Since the vulnerability requires user interaction, user awareness and training also play a role in mitigating risk. The absence of known active exploits currently reduces immediate risk but does not eliminate the threat, especially as exploit code is publicly available. European organizations using affected Koillection versions should prioritize patching to prevent potential exploitation that could impact service integrity and trust.

Summary

CVE-2025-9747 is a Cross-Site Request Forgery (CSRF) vulnerability identified in Koillection versions up to 1.6.18. The vulnerability resides in an unspecified function within the file assets/controllers/csrf_protection_controller.js, which is responsible for handling CSRF protection. The flaw allows an attacker to craft malicious requests that can be executed remotely without requiring authentication or elevated privileges. The vulnerability exploits the application's inadequate CSRF protection mechanism, enabling an attacker to trick authenticated users into submitting unwanted actions on their behalf. The vendor has addressed this issue in version 1.7.0 by switching to a newer, stateless token-based CSRF handling approach, which improves the robustness of the protection against such attacks. The CVSS v4.0 score is 5.3 (medium severity), reflecting that the attack vector is network-based, requires no privileges, no user authentication, but does require user interaction (e.g., clicking a malicious link). The impact on confidentiality is none, integrity is low, and availability is none, indicating that the primary risk is unauthorized actions performed by legitimate users without their consent. No known exploits are currently reported in the wild, but the exploit details have been publicly disclosed, increasing the risk of exploitation if unpatched. This vulnerability is relevant for any organization using Koillection versions 1.6.0 through 1.6.18, especially those exposing the application to external users or integrating it into web-facing services.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Sep 2025, 00:40 UTC

Technical details

References

Community reviews

Related threats