Unauthenticated File Upload in Magento Order Attributes

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 419matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The Amasty Order Attributes extension for Magento 2 contains a critical unauthenticated arbitrary file upload vulnerability (CVE-2026-53787) that exposes thousands of e-commerce stores to immediate compromise. By exploiting an unprotected upload endpoint, attackers can bypass all authentication and session validation to write arbitrary files—including PHP webshells—directly to the media directory. This vulnerability affects any Magento 2 installation running the vulnerable extension before version 4.0.0, with a CVSS score of 9.8 indicating near-total system compromise potential. The attack requires no authentication, no valid cart context, and no user interaction, making it trivial to exploit at scale. Once a PHP file is uploaded to a publicly accessible media directory with execution permissions, attackers gain remote code execution and complete control over the storefront, customer data, and payment systems.

Casky's skill mapping connects this vulnerability to three critical MITRE ATT&CK tactics: Initial Access (TA0001), where the unauthenticated upload endpoint serves as the foothold; Resource Development (TA0043), where attackers prepare malicious payloads; and Execution (TA0002), where uploaded PHP shells achieve code execution. Practitioners using Casky would detect attack patterns such as POST requests to `/upload` endpoints lacking authentication checks, file-type validation bypass indicators (PHP files accepted without extension filtering), and writes to web-accessible directories. Extended reasoning across the 419 matching skills would surface anomalies like: requests from non-authenticated sessions, suspicious file extensions in upload parameters, media directory activity outside normal business patterns, and POST submissions with Content-Type mismatches. Security teams would see findings flagging the absence of CSRF tokens, missing file-type whitelists, and execution permissions on upload directories—precisely the weaknesses that enable this zero-friction exploitation chain.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

419 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-53787.

analyzing-android-malware-with-apktool

malware analysis · medium

Run

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-bootkit-and-rootkit-samples

malware analysis · medium

Run

MITRE ATT&CK Techniques

TA0001 TA0043 TA0002

Investigate the attack patterns behind CVE-2026-53787

Casky has 419 skills that investigate the attack patterns behind CVE-2026-53787. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn