# CVE-2026-9187: Missing authorization in Abandoned Contact Form 7

> Unauthenticated attackers can permanently delete arbitrary posts or pages on WordPress sites using the Abandoned Contact Form 7 plugin due to missing authorization checks.

- **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:** 16 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-ff4x-rgp2-vm8c

## What is CVE-2026-9187?

CVE-2026-9187 is a medium-severity missing authorization vulnerability in zealopensource Abandoned Contact Form 7, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Abandoned Contact Form 7 plugin for WordPress is vulnerable to unauthorized arbitrary post deletion in versions up to, and including, 2.2. This is due to a missing capability check and missing nonce validation in the action__remove_abandoned() function, which is registered to both the wp_ajax_remove_abandoned and wp_ajax_nopriv_remove_abandoned hooks. The handler takes a user-supplied recover_id parameter from $_POST and passes it directly to wp_delete_post() with the force-delete flag set to true, without verifying that the ID belongs to the plugin's own cf7af_data post type. This makes it possible for unauthenticated attackers to permanently delete arbitrary posts, pages, or other content on the affected site by sending a single admin-ajax.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-9187 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9187 is a medium-severity missing authorization vulnerability in zealopensource Abandoned Contact Form 7, published on 16 Jun 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-9187 in the wild and no public exploit code.

Affected product: zealopensource Abandoned Contact Form 7. 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-9187/ (Markdown: https://insights.sbomify.com/CVE-2026-9187/index.md)
```

## Sources

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

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