# CVE-2025-54236: Adobe Commerce and Magento Improper Input Validation > Attackers can exploit improper input validation to achieve session takeover, compromising confidentiality and integrity without user interaction. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Yes, since 24 Oct 2025 (CISA KEV) - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 9 Sep 2025 - **Updated:** 24 Oct 2025 - **Also known as:** GHSA-wh92-6q6g-px7j ## What is CVE-2025-54236? CVE-2025-54236 is a critical vulnerability in Adobe Commerce, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2025-54236? 14 open source packages ship an affected version, including magento/community-edition and magento/project-community-edition. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `magento/community-edition` | Packagist | All versions | None | | `magento/community-edition` | Packagist | All versions | None | | `magento/community-edition` | Packagist | All versions to 2.4.5-p14 | None | | `magento/community-edition` | Packagist | All versions to 2.4.5-p14 | None | | `magento/community-edition` | Packagist | From 2.4.6-p1 to 2.4.6-p12 | None | | `magento/community-edition` | Packagist | From 2.4.6-p1 to 2.4.6-p12 | None | | `magento/community-edition` | Packagist | From 2.4.7-beta1 to 2.4.7-p7 | None | | `magento/community-edition` | Packagist | From 2.4.7-beta1 to 2.4.7-p7 | None | | `magento/community-edition` | Packagist | From 2.4.8-beta1 to 2.4.8-p2 | None | | `magento/community-edition` | Packagist | From 2.4.8-beta1 to 2.4.8-p2 | None | | `magento/community-edition` | Packagist | From 2.4.9-alpha1 to 2.4.9-alpha2 | None | | `magento/community-edition` | Packagist | From 2.4.9-alpha1 to 2.4.9-alpha2 | None | | `magento/project-community-edition` | Packagist | All versions to 2.0.2 | None | | `magento/project-community-edition` | Packagist | All versions to 2.0.2 | None | Products: Adobe Commerce, Adobe Commerce B2b, Adobe Magento. ## How do I fix CVE-2025-54236? No fix has been published for CVE-2025-54236 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Nov 2025. ## Is CVE-2025-54236 being exploited? Yes. Attackers have exploited CVE-2025-54236 in the wild since at least 24 Oct 2025. Public exploit code: - Patch for CVE-2025-54236(a.k.a Session Reaper) which allows customer account takeover and RCE under certain conditions. This patch is actually a Magento 2 extension and universal compatible for Magento 2.3 & 2.4. If you cannot upgrade Magento or cannot apply the official hotfix, try this one. (github_poc): https://github.com/wubinworks/magento2-session-reaper-patch - PoC Magento Session Reaper - CVE-2025-54236 (github_poc): https://github.com/alexb616/SessionReaper-CVE-2025-54236 - This is a tiny lab that simulates the core idea reported for CVE-2025-54236 (“SessionReaper”) (github_poc): https://github.com/amalpvatayam67/day01-sessionreaper-lab - Magento SessionReaper (metasploit) - cve-2025-54236 poc (github_poc): https://github.com/Baba01hacker666/cve-2025-54236 - SessionReaper-CVE-2025-54236 (github_poc): https://github.com/Jenderal92/magento-upload-auto-submit-zoneh ## Other vulnerabilities in Adobe Commerce - [CVE-2026-75650](https://insights.sbomify.com/CVE-2026-75650/): Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine (critical 10.0, exploited in the wild) - [CVE-2024-34102](https://insights.sbomify.com/CVE-2024-34102/): Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) (critical 9.8, exploited in the wild) - [CVE-2022-24086](https://insights.sbomify.com/CVE-2022-24086/): Adobe Commerce and Magento Open Source Improper Input Validation (critical 9.8, exploited in the wild) - [CVE-2026-48356](https://insights.sbomify.com/CVE-2026-48356/): Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type (critical 9.3, exploited in the wild) - [CVE-2026-71362](https://insights.sbomify.com/CVE-2026-71362/): Adobe Commerce and Magento Incorrect Authorization Vulnerability (critical 9.1, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-54236 and fix it if it is affected. What it is: CVE-2025-54236 is a critical vulnerability in Adobe Commerce, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2025-54236 in the wild since at least 24 Oct 2025. Affected packages and fixed versions: - magento/community-edition (Packagist): affected all versions; no fix listed - magento/community-edition (Packagist): affected all versions; no fix listed - magento/community-edition (Packagist): affected all versions up to 2.4.5-p14; no fix listed - magento/community-edition (Packagist): affected all versions up to 2.4.5-p14; no fix listed - magento/community-edition (Packagist): affected from 2.4.6-p1 up to 2.4.6-p12; no fix listed - magento/community-edition (Packagist): affected from 2.4.6-p1 up to 2.4.6-p12; no fix listed - magento/community-edition (Packagist): affected from 2.4.7-beta1 up to 2.4.7-p7; no fix listed - magento/community-edition (Packagist): affected from 2.4.7-beta1 up to 2.4.7-p7; no fix listed - magento/community-edition (Packagist): affected from 2.4.8-beta1 up to 2.4.8-p2; no fix listed - magento/community-edition (Packagist): affected from 2.4.8-beta1 up to 2.4.8-p2; no fix listed - magento/community-edition (Packagist): affected from 2.4.9-alpha1 up to 2.4.9-alpha2; no fix listed - magento/community-edition (Packagist): affected from 2.4.9-alpha1 up to 2.4.9-alpha2; no fix listed 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-2025-54236/ (Markdown: https://insights.sbomify.com/CVE-2025-54236/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54236 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54236 - OSV: https://osv.dev/vulnerability/CVE-2025-54236 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-54236/ Summaries are generated and may contain mistakes; the official description above is the record.