CVE-2025-60538
BaseFortify
Publication date: 2026-01-09
Last updated on: 2026-01-09
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| go-shiori | shiori | to 1.7.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-290 | This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Shiori version 1.7.4 and below is due to a lack of rate limiting on the login page. This means there are no restrictions on the number of password attempts an attacker can make. As a result, an attacker can perform a brute force attack by systematically trying many password combinations until they successfully authenticate, bypassing normal login protections. [1]
How can this vulnerability impact me? :
The vulnerability allows attackers to gain unauthorized access to the Shiori application by repeatedly guessing passwords without limitation. This can lead to compromised user accounts, potential data exposure, and unauthorized actions within the application, impacting the security and integrity of your system. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring login attempts to the Shiori application login page for an unusually high number of failed login attempts without any rate limiting or lockout. Using tools like Burp Suite to intercept and analyze POST login requests can help identify if the application allows unlimited password attempts. Specifically, employing Burp Suite's Intruder tool to simulate brute force attacks can confirm the lack of rate limiting. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing rate limiting or account lockout mechanisms on the login page to restrict the number of password attempts. Until an official patch or update is available, monitoring and blocking suspicious IP addresses performing multiple login attempts can help reduce risk. Additionally, consider using web application firewalls (WAF) to detect and block brute force attack patterns. [1]