# CVE-2025-48141: WordPress Multi CryptoCurrency Payments plugin <= 2.0.7 - SQL Injection Vulnerability

> An attacker can perform SQL injection attacks on the Multi CryptoCurrency Payments WordPress plugin to read or modify database contents.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-48f7-48wq-h8fq

## What is CVE-2025-48141?

CVE-2025-48141 is a critical SQL injection vulnerability in Alex Zaytseff Multi CryptoCurrency Payments, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Alex Zaytseff Multi CryptoCurrency Payments multi-crypto-currency-payment allows SQL Injection.This issue affects Multi CryptoCurrency Payments: from n/a through <= 2.0.7.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2025-48141 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48141 is a critical SQL injection vulnerability in Alex Zaytseff Multi CryptoCurrency Payments, published on 9 Jun 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-48141 in the wild and no public exploit code.

Affected product: Alex Zaytseff Multi CryptoCurrency Payments. 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-48141/ (Markdown: https://insights.sbomify.com/CVE-2025-48141/index.md)
```

## Sources

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

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