Adobe Commerce / Magento Improper Input Validation (CVE-2025-54236)
Detects exploitation of CVE-2025-54236, an improper input validation vulnerability in Adobe Commerce and Magento. This KEV-listed vulnerability allows attackers to submit maliciously crafted input to Commerce/Magento endpoints, potentially leading to remote code execution, unauthorized data access, or store compromise. Detection focuses on anomalous HTTP request patterns to Magento/Commerce endpoints, unexpected PHP execution, and indicators of post-exploitation activity.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- Adobe
- Product
- Commerce and Magento
Weakness (CWE)
Timeline
- Disclosed
- October 24, 2025
CVSS
What is CVE-2025-54236 Adobe Commerce / Magento Improper Input Validation (CVE-2025-54236)?
Adobe Commerce / Magento Improper Input Validation (CVE-2025-54236) (CVE-2025-54236) maps to the Initial Access and Execution and Persistence and Impact tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for Adobe Commerce / Magento Improper Input Validation (CVE-2025-54236), covering the data sources and telemetry it touches: IIS Logs, Azure Application Gateway, WAF/Proxy Logs, CommonSecurityLog. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
- Tactic
- Initial Access Execution Persistence Impact
let MagentoEndpoints = dynamic(['/rest/', '/api/', '/index.php/rest/', '/pub/index.php', '/graphql', '/downloader/', '/admin/']);
let SuspiciousPatterns = dynamic(['eval(', 'base64_decode', 'system(', 'exec(', 'passthru(', 'shell_exec', 'phpinfo', '<?php', 'assert(', 'preg_replace']);
union
(
W3CIISLog
| where csUriStem has_any (MagentoEndpoints)
| where csMethod in ('POST', 'PUT', 'PATCH')
| where scStatus in (200, 201, 500)
| where csUriQuery has_any (SuspiciousPatterns) or csBytes > 50000
| extend RequestPath = strcat(csUriStem, '?', csUriQuery)
),
(
AzureDiagnostics
| where Category == 'ApplicationGatewayAccessLog'
| where requestUri_s has_any (MagentoEndpoints)
| where httpMethod_s in ('POST', 'PUT', 'PATCH')
| where httpStatus_d in (200, 500)
| extend RequestPath = requestUri_s
),
(
CommonSecurityLog
| where DeviceVendor in ('Apache', 'nginx', 'F5', 'Imperva')
| where RequestURL has_any (MagentoEndpoints)
| where RequestMethod in ('POST', 'PUT', 'PATCH')
| extend RequestPath = RequestURL
)
| summarize RequestCount=count(), UniqueIPs=dcount(cIP), Paths=make_set(RequestPath, 20) by bin(TimeGenerated, 5m), cIP
| where RequestCount > 10 or UniqueIPs > 5
| extend AlertSeverity = iff(RequestCount > 50 or UniqueIPs > 20, 'Critical', 'High')
| project TimeGenerated, SourceIP=cIP, RequestCount, UniqueIPs, SuspiciousPaths=Paths, AlertSeverity Detects suspicious POST/PUT/PATCH requests to Adobe Commerce/Magento REST API, GraphQL, and admin endpoints that may indicate CVE-2025-54236 exploitation. Flags high-volume requests, oversized payloads, and requests with embedded code patterns.
Data Sources
Required Tables
False Positives
- Legitimate bulk API operations from integration partners or ERP systems sending large POST payloads
- Automated e-commerce workflows (order sync, inventory updates) triggering high request volumes
- Security scanners or penetration testing tools targeting the Magento application
- Load balancer health checks hitting REST endpoints repeatedly
Sigma rule & cross-platform mapping
The detection logic for Adobe Commerce / Magento Improper Input Validation (CVE-2025-54236) (CVE-2025-54236) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: network_connection
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2025-54236
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Magento REST API Malformed Input Fuzzing
Expected signal: Web server access logs should show POST requests to /rest/V1/products and /rest/V1/customers with large Content-Length values and HTTP 400/500 response codes
- Test 2PHP Web Shell Upload via Compromised Magento Admin
Expected signal: IIS/Apache logs showing POST to admin CMS endpoint; filesystem monitoring alerts on new .php file creation in pub/media/; process execution logs if PHP is evaluated
- Test 3Rapid Sequential API Endpoint Reconnaissance
Expected signal: Web server access logs showing rapid sequential POST requests to multiple /rest/V1/ endpoints from a single source IP within a short timeframe
Unlock Pro Content
Get the full detection package for CVE-2025-54236 including response playbook, investigation guide, and atomic red team tests.