Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-48176: Lylme Spage v1.9.5 is vulnerable to Incorrect Access Control

49
This month
CRITICAL 9.8REMOTEDOWNGRADE

CVE-2024-48176 is a critical-severity flaw (CVSS 9.8) affecting lylme spage. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 60%)
CISA exploited listNo
WeaknessCWE-863
Published2024-11-05
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: lylme

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

lylme lylme spage DOWNGRADE
Affected: 1.9.5
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.9.5
1. Check installed version
apt-cache policy lylme-spage || rpm -q lylme-spage || lylme-spage --version
2. No fixed release: DOWNGRADE to a release before 1.9.5 (Debian / Ubuntu)
apt-cache madison lylme-spage sudo apt install lylme-spage=<VERSION_BEFORE_1.9.5> sudo apt-mark hold lylme-spage
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list lylme-spage sudo dnf downgrade lylme-spage-<VERSION_BEFORE_1.9.5> sudo dnf versionlock add lylme-spage
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-48176?

lylme spage: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-48176 being exploited?

CVE-2024-48176 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-48176 affect?

CVE-2024-48176 affects lylme spage. Severity is critical (CVSS 9.8). 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

How urgent is CVE-2024-48176?

Priority 49/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.