# CVE-2026-85126: Crowdfundly <= 2.2.2 - Crowdfundly Manager+ Privilege Escalation

> Low-privileged users can escalate to administrator via missing capability checks in AJAX actions, leading to full site takeover.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-jpjw-mhpj-4h5q

## What is CVE-2026-85126?

CVE-2026-85126 is a high-severity vulnerability in Unknown Crowdfundly, published on 11 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Crowdfundly WordPress plugin through 2.2.2 does not have capability checks on some of its AJAX actions, allowing users holding one of its own low privileged roles to grant themselves the administrator role or arbitrary capabilities, leading to a full site takeover.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-85126 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85126 is a high-severity vulnerability in Unknown Crowdfundly, published on 11 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85126 in the wild and no public exploit code.

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

## Sources

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

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