VulnerabilityPublished 19 Oct 2026

CVE-2026-107084: CSRF

Source CVE Database V5

Not known to be exploited.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Medium

Rated Medium by the CNA (mitre) · CVSS not yet scored by NVD

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

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), 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

AI-suggested

Until a fix is available, administrators should restrict access to the affected functionality, implement additional CSRF protections if possible, and avoid performing administrative actions via GET requests. Monitoring for suspicious activity related to loan history maintenance is advisable.

Description

Slims (Senayan Library Management Systems) version 9.8.0 contains a cross-site request forgery (CSRF) vulnerability in the loan history maintenance functionality. The vulnerability arises because the action=run GET parameter triggers privileged, destructive operations without requiring a CSRF token or POST confirmation. This flaw allows an attacker to cause data loss of loan history records via unauthorized requests.

Impact

Successful exploitation results in loss of loan history records due to unauthorized execution of destructive operations. This compromises data integrity within the library management system but does not indicate direct code execution or broader system compromise based on the available information.

Summary

CVE-2026-107084 describes a CSRF vulnerability in Slims 9.8.0 where the admin/modules/circulation/loan_history_maintenance.php script accepts an action=run GET parameter that performs privileged destructive operations without CSRF protections such as tokens or POST method enforcement. This lack of validation enables attackers to induce unintended destructive actions on loan history data by tricking authenticated administrators into executing crafted requests.

References

Community reviews

Loading reviews…