# CVE-2021-25119: AGIL <= 1.0 - Admin+ Arbitrary File Upload

> Administrators can upload arbitrary files via zip extraction, leading to remote code execution in the AGIL WordPress plugin.

- **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:** 16 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jj2q-3vcq-6pjc

## What is CVE-2021-25119?

CVE-2021-25119 is a high-severity vulnerability in Unknown AGIL(Automatic Grid Image Listing), published on 16 May 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The AGIL WordPress plugin through 1.0 accepts all zip files and automatically extracts the zip file without validating the extracted file type. Allowing high privilege users such as admin to upload an arbitrary file like PHP, leading to RCE

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Wpsocket Automatic Grid Image Listing.

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

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

## Is CVE-2021-25119 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-25119 is a high-severity vulnerability in Unknown AGIL(Automatic Grid Image Listing), published on 16 May 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25119 in the wild and no public exploit code.

Affected product: Unknown AGIL(Automatic Grid Image Listing). 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-25119/ (Markdown: https://insights.sbomify.com/CVE-2021-25119/index.md)
```

## Sources

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

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