CVE-2025-4543: A vulnerability, which was classified as critical, was found in LyLme Spage 2.1

This week

HIGH 7.3REMOTEDOWNGRADE

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

A vulnerability, which was classified as critical, was found in LyLme Spage 2.1. This affects an unknown part of the file lylme_spage/blob/master/admin/ajax_link.php. The manipulation of the argument sort leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Why this priority

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

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

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-74, CWE-89
Published	2025-05-11
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: lylme

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

Am I affected?

Timeline

2025-05-11 18:15 UTCPublished CVE record published
2026-06-17 09:33 UTCUpdated Record last modified

lylme lylme spage DOWNGRADE

Affected: 2.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1.0

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 2.1.0 (Debian / Ubuntu)

apt-cache madison lylme-spage sudo apt install lylme-spage=<VERSION_BEFORE_2.1.0> 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_2.1.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-2025-4543?

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

Is CVE-2025-4543 being exploited?

CVE-2025-4543 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-2025-4543 affect?

CVE-2025-4543 affects lylme spage. Severity is high (CVSS 7.3). A vulnerability, which was classified as critical, was found in LyLme Spage 2.1. This affects an unknown part of the file lylme_spage/blob/master/admin/ajax_link.php. The manipulation of the argument sort leads to sql injection. It is possi

How urgent is CVE-2025-4543?

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

Software pages

PHP vulnerabilities

Related CVEs

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-48357 CRITICAL 9.8 UPGRADE LyLme Spage 1.2.0 through 1.6.0 is vulnerable to SQL Injection via /admin/apply.php.
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