# CVE-2026-87981: Missing authorization in Paymob for WooCommerce

> Contributors can delete or modify payment gateway settings and credentials due to missing capability checks in AJAX actions.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-pgxh-7vg6-g5g2

## What is CVE-2026-87981?

CVE-2026-87981 is a medium-severity missing authorization vulnerability in Unknown Paymob for WooCommerce, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Paymob for WooCommerce WordPress plugin before 4.1.14 does not perform a capability check on several admin AJAX actions that manage its payment-gateway configuration, allowing users with contributor-level access to delete, wipe, or modify that configuration, including the stored payment credentials.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-87981 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87981 is a medium-severity missing authorization vulnerability in Unknown Paymob for WooCommerce, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-87981 in the wild and no public exploit code.

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

## Sources

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

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