# CVE-2021-25116: Enqueue Anything <= 1.0.1 - Subscriber+ Arbitrary Asset/Post Deletion

> Low-privilege users can delete arbitrary assets and trash posts due to missing authorization and CSRF checks in the Enqueue Anything plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qj28-v8qh-ccqw

## What is CVE-2021-25116?

CVE-2021-25116 is a medium-severity missing authorization vulnerability in Unknown Enqueue Anything, published on 13 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Enqueue Anything WordPress plugin through 1.0.1 does not have authorisation and CSRF checks in the remove_asset AJAX action, and does not ensure that the item to be deleted is actually an asset. As a result, low privilege users such as subscriber could delete arbitrary assets, as well as put arbitrary posts in the trash.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-25116?

It affects 1 product.


Products: Enqueue Anything Project Enqueue Anything.

## How do I fix CVE-2021-25116?

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

## Is CVE-2021-25116 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25116 and fix it if it is affected.

What it is: CVE-2021-25116 is a medium-severity missing authorization vulnerability in Unknown Enqueue Anything, published on 13 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25116 in the wild and no public exploit code.

Affected product: Unknown Enqueue Anything. 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-2021-25116/ (Markdown: https://insights.sbomify.com/CVE-2021-25116/index.md)
```

## Sources

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

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