# CVE-2026-81648: Missing authorization in CryptoPayment Gateway

> Unauthenticated attackers can delete arbitrary files, modify payment settings, and steal wallet credentials due to missing authorization checks in the AJAX router.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-9r3q-6qw8-8pm7

## What is CVE-2026-81648?

CVE-2026-81648 is a critical missing authorization vulnerability in Unknown CryptoPayment Gateway, published on 13 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CryptoPayment Gateway WordPress plugin from 1.2.1 to 1.2.2 does not apply an authorization check on one of its AJAX endpoints, allowing unauthenticated users to invoke administrative operations, including deleting arbitrary files on the server, overwriting the payment gateway configuration and recovering stored wallet credentials in cleartext.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-81648?


## How do I fix CVE-2026-81648?

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

## Is CVE-2026-81648 being exploited?

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

Public exploit code:

- CVE-2026-81648 - WordPress - CryptoPayment Gateway - Critical 10.0 - Unauthenticated POST /wp-content/plugins/cryptopayment-gateway/vendor/cryptd/ajax.php - Arbitrary File Deletion (github_poc): https://github.com/abraxas/CVE-2026-81648

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81648 and fix it if it is affected.

What it is: CVE-2026-81648 is a critical missing authorization vulnerability in Unknown CryptoPayment Gateway, published on 13 Sep 2026. 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-2026-81648 in the wild and no public exploit code.

Affected product: Unknown CryptoPayment Gateway. 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-2026-81648/ (Markdown: https://insights.sbomify.com/CVE-2026-81648/index.md)
```

## Sources

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

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