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

- Exploited (CISA KEV): no
- Published: 2026-06-12
- CVSS: 9.3 CRITICAL (v4.0)
- EPSS: 5.6% (93th percentile)
- CWE: CWE-434

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.

## Edge WAF coverage (claimed by vendors, not measured)

| Vendor | Status | First rule | Days after publication |
|---|---|---|---|
| Cloudflare | No public claim | — | — |
| AWS | No public claim | — | — |
| Microsoft Azure | No public claim | — | — |
| Google Cloud | No public claim | — | — |
| Fastly | Before feed history | — | — |
| F5 | Rule published | 2026-09-16 | 96 |
| Akamai | No public source | — | — |
| OWASP CRS | No public claim | — | — |

### F5

- 2026-09-16 · new · rule 200020246
  > Added: signature 200020246 "Amasty Order Attributes Malicious File Upload" (Malicious File Upload, risk High), systems: Other Web Server. References: CVE-2026-53787.
  Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog

## Our test (measured)

- OWASP Core Rule Set 4.25.0, paranoia level 1, anomaly threshold 5, default CRS settings: passed (0 of 5 requests blocked), template CVE-2026-53787, 2026-11-02
- OWASP Core Rule Set 4.25.0, paranoia level 2, anomaly threshold 5, default CRS settings: partial (3 of 5 requests blocked), template CVE-2026-53787, 2026-11-02

"No public claim" means no vendor statement names this CVE; "Before feed history" means the CVE is older than the vendor feed. In both cases generic rules may still block it.

HTML: https://cve.vigilbase.com/cve/CVE-2026-53787 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2026-53787