# CVE-2026-85530: GiveWP < 4.16.8.1 - Unauthenticated Account Takeover via Donor Email Sanitization Mismatch

> Unauthenticated attackers can take over any user account, including administrators, due to inconsistent email normalization in the GiveWP plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-f8r4-h4wf-5gg7

## What is CVE-2026-85530?

CVE-2026-85530 is a high-severity authentication bypass vulnerability in Unknown GiveWP, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The GiveWP  WordPress plugin before 4.16.8.1 does not consistently normalise a donor's e-mail address between the value it stores and the value it later uses to look that donor up, allowing unauthenticated users to be resolved as an arbitrary donor and to set the WordPress password of any user account linked to one, including an administrator's.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-85530 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85530 is a high-severity authentication bypass vulnerability in Unknown GiveWP, published on 16 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-85530 in the wild and no public exploit code.

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

## Sources

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

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