# CVE-2026-96896: Malcure Malware Shield < 19.9.7 - Multisite Subsite Admin+ Arbitrary File Write and Deletion via wpmr_ajax_request

> Subsite administrators can write and delete arbitrary files due to missing authorization checks, potentially leading to remote code execution.

- **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:** 27 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-2hrm-754x-j578

## What is CVE-2026-96896?

CVE-2026-96896 is a high-severity missing authorization vulnerability in Unknown Malcure Malware Shield — Removal, Repair, Monitor, published on 27 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Malcure Malware Shield — Removal, Repair, Monitor WordPress plugin before 19.9.7 does not perform an authorisation check on one of its AJAX actions, allowing users with a subsite administrator role on a multisite network to write and delete arbitrary files in the network's shared filesystem, which can lead to remote code execution.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-96896 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96896 is a high-severity missing authorization vulnerability in Unknown Malcure Malware Shield — Removal, Repair, Monitor, published on 27 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-96896 in the wild and no public exploit code.

Affected product: Unknown Malcure Malware Shield — Removal, Repair, Monitor. 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-96896/ (Markdown: https://insights.sbomify.com/CVE-2026-96896/index.md)
```

## Sources

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

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