Vulnerability report

Active exploitation observed Confirmed confidence In CISA KEV

CVE-2025-54236

Adobe Commerce

Adobe Commerce · 0 to <= 2.4.4-p15

Severity
CVSS 9.1 · Critical
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
94.5%
First observed
12 Jun 2026
Last observed
01 Oct 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2025-54236 is an unauthenticated vulnerability affecting Adobe Commerce. Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Improper Input...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence. Listed in CISA KEV. Also confirmed by third-party sources.

Who is affected?

Adobe Commerce 0 to <= 2.4.4-p15.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

Adobe Commerce

Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Improper Input Validation vulnerability. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high.

Exploitation of this issue does not require user interaction.

Adobe Affected
Adobe Commerce
Through 2.4.4-p15
View vendor advisory (opens in new tab)
Published
09 Sep 2025
Exploitation Reported
01 Jun 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nuclei_scanner cisa

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CVE

Recorded 01 Jun 2026

A trusted third party reported exploitation.

Active exploitation observed

Previdian sensor

First observed 11 Sep 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

Proof of concept available

Nuclei Templates

Recorded 12 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
Adobe Commerce Security Bulletins First 2025-09-09 13:20 UTC
CVE 2026-06-01 10:42 UTC
CISA 2026-06-02 14:05 UTC
The Shadowserver 2026-07-08 00:00 UTC
Tenable Blog 2026-09-08 14:00 UTC
Previdian Sensors 2026-09-11 14:55 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.

36

Attempts observed

22

Unique attacker IPs

10

Attacker countries

BG · CH · DE · HK · ID · JP · NL · TW · US · YE

10

Sensors observed

CVE-2025-54236 exploitation attempts over the last 85 days

Daily events observed by Previdian sensors

Updated 10 Oct 2026

0
1
0
0
0
0
1
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
1
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
4
1
0
0
4
0
0
0
0
0
1
5
0
1
0
0
5
1
0
6
0
1
0
0
0
0
0
0
0
0
0
18 Jul 4 Aug 21 Aug 7 Sep 10 Oct

First observed 12 Jun 2026 · Last observed 01 Oct 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
4
13
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Attacker IP Indicators

Attacker IP indicators observed · available in Pro and Enterprise.

Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.

Learn about Pro API access

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.1 Critical

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

94.5%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Recent mention · Tenable Blog

StyleSmuggler (CVE-2026-75650): Frequently asked questions about Adobe Commerce and Magento zero-day

A critical unauthenticated remote code execution (RCE) zero-day in Adobe Commerce and Magento Open Source, dubbed StyleSmuggler, has been actively exploited since September 4 with attacks observed three days before a vendor patch became available.Key takeawaysCVE-2026-75650 is...

Read full advisory

All Mentions

Recent mention · Tenable Blog

StyleSmuggler (CVE-2026-75650): Frequently asked questions about Adobe Commerce and Magento zero-day

Tenable Blog · 08 Sep 2026

A critical unauthenticated remote code execution (RCE) zero-day in Adobe Commerce and Magento Open Source, dubbed StyleSmuggler, has been actively exploited since September 4 with attacks observed three days before a vendor patch became available.Key takeawaysCVE-2026-75650 is a critical remote code execution vulnerability in Adobe Commerce, Adobe Commerce B2B and Magento Open Source that can be triggered without authentication.Active exploitation of CVE-2026-75650 began on September 4, 2026, three days before Adobe released a hotfix, with multiple victim stores confirmed across different...

Recent mention · Adobe Commerce Security Bulletins

APSB25-88 : Adobe Commerce | Improper Input Validation (CWE-20)

Adobe Commerce Security Bulletins · 09 Sep 2025

CVE-2025-54236 Adobe Commerce | Improper Input Validation (CWE-20) Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Improper Input Validation vulnerability. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high. Exploitation of this issue does not require user interaction.

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation

  1. 14:43 UTC

    Indicators of compromise added (15)

    Indicators of compromise recorded

  2. 14:43 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

  3. 14:00 UTC

    KEV confirmed by Tenable Blog

    Exploitation attested by an external source

  4. 00:00 UTC

    KEV confirmed by The Shadowserver

    Exploitation attested by an external source

  5. 14:21 UTC

    Public PoC available

    Public proof-of-concept code published

  6. 14:05 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  7. 15:34 UTC

    Nuclei template available

    Scanner coverage available

  8. 10:42 UTC

    KEV confirmed by CVE

    Exploitation attested by an external source

  9. 13:20 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  10. 13:20 UTC

    CVE published

    Vulnerability disclosed publicly

  11. 21:15 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2025-54236

Free JSON includes basic KEV fields
{
  "cve_id": "CVE-2025-54236",
  "confidence": "Confirmed",
  "cvss_score": 9.1,
  "cvss_estimated": false,
  "epss_score": 0.94532,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 36, "sensors": 10 }
}