Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-2218: A vulnerability has been found in LoveCards LoveCardsV2 up to 2.3.2 and classified as critical

37
Routine
MEDIUM 5.3REMOTEUPGRADE

CVE-2025-2218 is a medium-severity flaw (CVSS 5.3) affecting lovecards. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability has been found in LoveCards LoveCardsV2 up to 2.3.2 and classified as critical. This vulnerability affects unknown code of the file /api/system/other of the component Setting Handler. The manipulation leads to improper access controls. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.8% (top 45%)
CISA exploited listNo
WeaknessCWE-266, CWE-284
Published2025-03-12
Last modified2026-06-17
Publisher (CNA): VulDB · Vendor: lovecards

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

lovecards lovecards UPGRADE
Affected: >= 2.1.1 and <= 2.3.2
Fixed in: newer than 2.3.2
Safe to downgrade to: a release before 2.1.1
1. Check installed version
apt-cache policy lovecards || rpm -q lovecards || lovecards --version
2. UPGRADE to newer than 2.3.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade lovecards
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade lovecards
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 2.1.1 (Debian / Ubuntu)
apt-cache madison lovecards sudo apt install lovecards=<VERSION_BEFORE_2.1.1> sudo apt-mark hold lovecards
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list lovecards sudo dnf downgrade lovecards-<VERSION_BEFORE_2.1.1> sudo dnf versionlock add lovecards
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-2218?

lovecards: upgrade to newer than 2.3.2. Exact commands for each OS are on this page.

Is CVE-2025-2218 being exploited?

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

CVE-2025-2218 affects lovecards. Severity is medium (CVSS 5.3). A vulnerability has been found in LoveCards LoveCardsV2 up to 2.3.2 and classified as critical. This vulnerability affects unknown code of the file /api/system/other of the component Setting Handler. The manipulation leads to improper acces

How urgent is CVE-2025-2218?

Priority 37/100. 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.