# CVE-2023-1546: MyCryptoCheckout < 2.124 - Reflected XSS

> Attackers can inject malicious scripts via unescaped URLs in the MyCryptoCheckout WordPress plugin, potentially compromising user sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 May 2023
- **Updated:** 30 Jan 2025
- **Also known as:** GHSA-c6vc-gphj-54v8

## What is CVE-2023-1546?

CVE-2023-1546 is a medium-severity cross-site scripting vulnerability in Unknown MyCryptoCheckout, published on 2 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The MyCryptoCheckout WordPress plugin before 2.124 does not escape some URLs before outputting them in attributes, leading to Reflected Cross-Site Scripting

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-1546?

It affects 1 product.


Products: Plainviewplugins Mycryptocheckout.

## How do I fix CVE-2023-1546?

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

## Is CVE-2023-1546 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1546 exists.

Public exploit code:

- MyCryptoCheckout < 2.124 - Cross-Site Scripting (nuclei): http/cves/2023/CVE-2023-1546.yaml

## Other vulnerabilities in Unknown MyCryptoCheckout

- [CVE-2023-41693](https://insights.sbomify.com/CVE-2023-41693/): WordPress MyCryptoCheckout Plugin <= 2.125 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1546 and fix it if it is affected.

What it is: CVE-2023-1546 is a medium-severity cross-site scripting vulnerability in Unknown MyCryptoCheckout, published on 2 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1546 exists.

Affected product: Unknown MyCryptoCheckout. 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-2023-1546/ (Markdown: https://insights.sbomify.com/CVE-2023-1546/index.md)
```

## Sources

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

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