# CVE-2026-86809: Persian Elementor < 2.8.2 - Unauthenticated ZarinPal Payment Callback Authority Bypass

> Unauthenticated attackers can complete pending orders by reusing payment authorities from other transactions, bypassing payment verification in the Persian Elementor plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-ff8m-xxv4-v5mc

## What is CVE-2026-86809?

CVE-2026-86809 is a medium-severity vulnerability in Unknown Persian Elementor, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Persian Elementor WordPress plugin from 2.7.10 before 2.8.2 does not verify that the payment authority returned to its ZarinPal payment callback belongs to the transaction being completed, allowing unauthenticated attackers to complete a pending order using a valid payment authority obtained from a different transaction.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-86809 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86809 is a medium-severity vulnerability in Unknown Persian Elementor, published on 11 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-86809 in the wild and no public exploit code.

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

## Sources

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

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