CVE-2025-2219: A vulnerability was found in LoveCards LoveCardsV2 up to 2.3.2 and classified as critical

This month

HIGH 7.3REMOTEUPGRADE

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

A vulnerability was found in LoveCards LoveCardsV2 up to 2.3.2 and classified as critical. This issue affects some unknown processing of the file /api/upload/image. The manipulation of the argument file leads to unrestricted upload. The attack may 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

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 48%)
CISA exploited list	No
Weakness	CWE-284, CWE-434
Published	2025-03-12
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: lovecards

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

Am I affected?

Timeline

2025-03-12 01:15 UTCPublished CVE record published
2026-06-17 09:06 UTCUpdated Record last modified

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-2219?

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

Is CVE-2025-2219 being exploited?

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

CVE-2025-2219 affects lovecards. Severity is high (CVSS 7.3). A vulnerability was found in LoveCards LoveCardsV2 up to 2.3.2 and classified as critical. This issue affects some unknown processing of the file /api/upload/image. The manipulation of the argument file leads to unrestricted upload. The att

How urgent is CVE-2025-2219?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

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

References

← Back to latest CVEs