CVE-2024-48357: LyLme Spage 1.2.0 through 1.6.0 is vulnerable to SQL Injection via /admin/apply.php.

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2024-48357 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 1.2.0 through 1.6.0 is vulnerable to SQL Injection via /admin/apply.php.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 53%)
CISA exploited list	No
Weakness	CWE-89
Published	2024-10-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: lylme

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

Am I affected?

Timeline

2024-10-28 20:15 UTCPublished CVE record published
2026-06-17 07:58 UTCUpdated Record last modified

lylme lylme spage UPGRADE

Affected: >= 1.2.0 and <= 1.6.0

Fixed in: newer than 1.6.0

Safe to downgrade to: a release before 1.2.0

1. Check installed version

apt-cache policy lylme-spage || rpm -q lylme-spage || lylme-spage --version

2. UPGRADE to newer than 1.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade lylme-spage

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade lylme-spage

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.2.0 (Debian / Ubuntu)

apt-cache madison lylme-spage sudo apt install lylme-spage=<VERSION_BEFORE_1.2.0> sudo apt-mark hold lylme-spage

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list lylme-spage sudo dnf downgrade lylme-spage-<VERSION_BEFORE_1.2.0> 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-48357?

lylme spage: upgrade to newer than 1.6.0. Exact commands for each OS are on this page.

Is CVE-2024-48357 being exploited?

CVE-2024-48357 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-48357 affect?

CVE-2024-48357 affects lylme spage. Severity is critical (CVSS 9.8). LyLme Spage 1.2.0 through 1.6.0 is vulnerable to SQL Injection via /admin/apply.php.

How urgent is CVE-2024-48357?

Priority 56/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

CVE-2025-4543 HIGH 7.3 DOWNGRADE A vulnerability, which was classified as critical, was found in LyLme Spage 2.1
CVE-2024-9790 MEDIUM 4.7 DOWNGRADE A vulnerability was found in LyLme_spage 1.9.5
CVE-2024-9789 MEDIUM 4.7 DOWNGRADE A vulnerability was found in LyLme_spage 1.9.5 and classified as critical
CVE-2024-9788 MEDIUM 4.7 DOWNGRADE A vulnerability has been found in LyLme_spage 1.9.5 and classified as critical
CVE-2024-48356 CRITICAL 9.8 UPGRADE LyLme Spage <=1.6.0 is vulnerable to SQL Injection via /admin/group.php.

References

← Back to latest CVEs