Skip to main content
VulnerabilityPublished Updated

CVE-2024-48176: lylme-spage · Incorrect Authorization

Affects lylme-spageSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2024

  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
npmlylme-spagepkg:npm/lylme-spageOther threatsAffected
  • =1.9.5
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 CVE-2024-48176, organizations should implement immediate compensating controls while awaiting official patches. These include: 1) Deploying network-level protections such as Web Application Firewalls (WAFs) configured to detect and block brute-force login attempts and rate-limit requests to the login endpoint. 2) Implementing IP blacklisting or throttling to restrict repeated login attempts from the same source. 3) Enforcing strong password policies and encouraging multi-factor authentication (MFA) if supported by the system. 4) Monitoring login logs for unusual patterns indicative of brute-force attacks and alerting security teams promptly. 5) If possible, modifying the application or using custom scripts to refresh verification codes after each failed login attempt to prevent automated guessing. 6) Restricting backend access to trusted networks or VPNs to reduce exposure. 7) Planning for rapid patch deployment once an official fix is released by the vendor. 8) Conducting regular security assessments and penetration testing to identify similar weaknesses.

Description

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.

References

Community reviews

Loading reviews…