# CVE-2026-53787: Amasty Order Attributes for Magento 2 < 4.0.0 Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files, including PHP, to achieve remote code execution or host malware on Magento 2 stores.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 13 Jun 2026
- **Also known as:** GHSA-mgg8-gq8g-gq88

## What is CVE-2026-53787?

CVE-2026-53787 is a critical vulnerability in Amasty Order Attributes for Magento 2, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Amasty Order Attributes for Magento 2 before version 4.0.0 contains an unauthenticated arbitrary file upload vulnerability that allows unauthenticated attackers to write arbitrary files to the store's media directory by submitting files of any type or name to the upload endpoint without authentication, session validation, or cart context. Attackers can upload PHP files to achieve remote code execution on servers where the media directory permits PHP execution, or alternatively enable malware hosting, stored cross-site scripting via HTML or SVG uploads, and path traversal to write files outside the intended upload directory.

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

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


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

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

## Is CVE-2026-53787 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53787 exists.

Public exploit code:

- CVE-2026-53787 Amasty Order Attribute (AOA) file upload exploit, modified to support the upload of HTML files instead of TXT files. (github_poc): https://github.com/MRdark-ops/CVE-2026-53787-poc
- A Secure Version of CVE-2026-53787 Amasty Order Attribute File Upload Exploit,with the modification of file upload of txt to html. (github_poc): https://github.com/elitexspam/Def4cer
- Magento 2 Amasty Order Attributes < 4.0.0 - Unauthenticated Arbitrary File Upload (nuclei): http/cves/2026/CVE-2026-53787.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53787 is a critical vulnerability in Amasty Order Attributes for Magento 2, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53787 exists.

Affected product: Amasty Order Attributes for Magento 2. 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-53787/ (Markdown: https://insights.sbomify.com/CVE-2026-53787/index.md)
```

## Sources

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

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