# CVE-2025-3811: WPBookit <= 1.0.2 - Insecure Direct Object Reference to Unauthenticated Privilege Escalation via Email Update

> Unauthenticated attackers can change arbitrary user emails to reset passwords and take over accounts, including administrators, due to missing identity validation.

- **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:** 9 May 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v5rp-5hx5-3vwq

## What is CVE-2025-3811?

CVE-2025-3811 is a critical authentication bypass vulnerability in iqonicdesign WPBookit, published on 9 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WPBookit plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.0.2. This is due to the plugin not properly validating a user's identity prior to updating their details like email through the edit_newdata_customer_callback() function. This makes it possible for unauthenticated attackers to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Iqonic Wpbookit.

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

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

## Is CVE-2025-3811 being exploited?

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

## Other vulnerabilities in iqonicdesign WPBookit

- [CVE-2025-6058](https://insights.sbomify.com/CVE-2025-6058/): WPBookit <= 1.0.4 - Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2025-3810](https://insights.sbomify.com/CVE-2025-3810/): WPBookit <= 1.0.2 - Insecure Direct Object Reference to Unauthenticated Privilege Escalation via Account Takeover (critical 9.8)
- [CVE-2025-0357](https://insights.sbomify.com/CVE-2025-0357/): WPBookit <= 1.6.9 - Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2024-10215](https://insights.sbomify.com/CVE-2024-10215/): WPBookit <= 1.6.4 - Unauthenticated Arbitrary User Password Change (critical 9.8)
- [CVE-2024-54280](https://insights.sbomify.com/CVE-2024-54280/): WordPress WPBookit plugin <= 1.6.0 - SQL Injection vulnerability (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3811 is a critical authentication bypass vulnerability in iqonicdesign WPBookit, published on 9 May 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-3811 in the wild and no public exploit code.

Affected product: iqonicdesign WPBookit. 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-3811/ (Markdown: https://insights.sbomify.com/CVE-2025-3811/index.md)
```

## Sources

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

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