# CVE-2025-6688: Simple Payment 1.3.6 - 2.3.8 - Authentication Bypass to Admin

> Unauthenticated attackers can bypass authentication to log in as administrators due to improper identity verification in the Simple Payment plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 27 Jun 2025
- **Updated:** 27 Jun 2025
- **Also known as:** GHSA-x3mp-x433-h32f

## What is CVE-2025-6688?

CVE-2025-6688 is a critical authentication bypass vulnerability in idokd Simple Payment, published on 27 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Simple Payment plugin for WordPress is vulnerable to Authentication Bypass in versions 1.3.6 to 2.3.8. This is due to the plugin not properly verifying a user's identity prior to logging them in through the create_user() function. This makes it possible for unauthenticated attackers to log in as administrative users.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Idokd Simple Payment.

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

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

## Is CVE-2025-6688 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6688 is a critical authentication bypass vulnerability in idokd Simple Payment, published on 27 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-6688 in the wild and no public exploit code.

Affected product: idokd Simple Payment. 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-6688/ (Markdown: https://insights.sbomify.com/CVE-2025-6688/index.md)
```

## Sources

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

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