# CVE-2025-2218: LoveCards LoveCardsV2 Setting other access control

> Remote attackers can bypass access controls on the Setting Handler API to read or modify system settings in LoveCards V2.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2025
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-mc9p-xqj3-6mx8

## What is CVE-2025-2218?

CVE-2025-2218 is a medium-severity missing authorization vulnerability in LoveCardsV2, published on 12 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-2218?

It affects 1 product.


Products: Lovecards Lovecards.

## How do I fix CVE-2025-2218?

No fix has been published for CVE-2025-2218 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2218 being exploited?

There is no known exploitation of CVE-2025-2218 in the wild and no public exploit code.

## Other vulnerabilities in LoveCardsV2

- [CVE-2025-2219](https://insights.sbomify.com/CVE-2025-2219/): LoveCards LoveCardsV2 image unrestricted upload (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2218 and fix it if it is affected.

What it is: CVE-2025-2218 is a medium-severity missing authorization vulnerability in LoveCardsV2, published on 12 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2218 in the wild and no public exploit code.

Affected product: LoveCardsV2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2218/ (Markdown: https://insights.sbomify.com/CVE-2025-2218/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2218
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2218
- OSV: https://osv.dev/vulnerability/CVE-2025-2218

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2218/
Summaries are generated and may contain mistakes; the official description above is the record.