CVE-2024-48176
First published: Tue Nov 05 2024(Updated: )
Lylme Spage v1.9.5 is vulnerable to Incorrect Access Control. There is no limit on the number of login attempts, and the verification code will not be refreshed after a failed login, which allows attackers to blast the username and password and log into the system backend.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| LyLme Spage | ||
| LyLme Spage | =1.9.5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2024-48176?
CVE-2024-48176 is classified as a high severity vulnerability due to its potential for exploitation through unlimited login attempts.
How do I fix CVE-2024-48176?
To mitigate CVE-2024-48176, implement account lockout mechanisms and ensure that verification code refreshes after each failed login attempt.
What systems are affected by CVE-2024-48176?
CVE-2024-48176 specifically affects Lylme Spage version 1.9.5.
What kind of attacks can be performed due to CVE-2024-48176?
An attacker can perform brute force attacks to gain unauthorized access to the system backend due to the lack of login attempt limits.
Is there a workaround for CVE-2024-48176 until a patch is available?
As a temporary workaround for CVE-2024-48176, you can enforce stricter password policies and monitor login attempts for suspicious activity.
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- agent/severity
- agent/weakness
- agent/event
- agent/last-modified-date
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- vendor/lylme
- canonical/lylme spage
- version/lylme spage/1.9.5