# CVE-2026-1982: Persian Elementor (المنتور فارسی) <= 2.8.1 - Unauthenticated Price Manipulation via ZarinPal Widget

> Unauthenticated attackers can manipulate payment amounts in the Persian Elementor plugin by bypassing server-side validation, leading to financial fraud.

- **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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-4hpv-v74p-q5cg

## What is CVE-2026-1982?

CVE-2026-1982 is a medium-severity vulnerability in mohammadr3z المنتور فارسی, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Persian Elementor (المنتور فارسی) plugin for WordPress is vulnerable to Price Manipulation in all versions up to, and including, 2.8.1. This is due to the plugin trusting a user-supplied payment amount without server-side validation against the configured ZarinPal widget price. This makes it possible for unauthenticated attackers to submit arbitrary payment amounts to the ZarinPal gateway via the 'amount' parameter.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

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


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

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

## Is CVE-2026-1982 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1982 is a medium-severity vulnerability in mohammadr3z المنتور فارسی, published on 30 Jul 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-1982 in the wild and no public exploit code.

Affected product: mohammadr3z المنتور فارسی. 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-1982/ (Markdown: https://insights.sbomify.com/CVE-2026-1982/index.md)
```

## Sources

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

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