# CVE-2023-0443: AnyWhere Elementor < 1.2.8 - Freemius API Key Disclosure

> An attacker can obtain a Freemius Secret Key to fraudulently purchase pro subscriptions using test credit cards.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-frc2-4fxv-jmxx

## What is CVE-2023-0443?

CVE-2023-0443 is a medium-severity vulnerability in Unknown AnyWhere Elementor, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AnyWhere Elementor WordPress plugin before 1.2.8 discloses a Freemius Secret Key which could be used by an attacker to purchase the pro subscription using test credit card numbers without actually paying the amount. Such key has been revoked.

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

It affects 1 product.


Products: Wpvibes Anywhere Elementor.

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

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

## Is CVE-2023-0443 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-0443 is a medium-severity vulnerability in Unknown AnyWhere Elementor, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0443 exists.

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

## Sources

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

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