# CVE-2025-54253: Adobe Experience Manager Forms Code Execution

> Attackers can bypass security mechanisms to execute arbitrary code in Adobe Experience Manager without user interaction.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Oct 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-7mcc-8f7p-x6v7

## What is CVE-2025-54253?

CVE-2025-54253 is a critical missing authorization vulnerability in Adobe Experience Manager, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Adobe Experience Manager versions 6.5.23 and earlier are affected by a Misconfiguration vulnerability that could result in arbitrary code execution. An attacker could leverage this vulnerability to bypass security mechanisms and execute code. Exploitation of this issue does not require user interaction and scope is changed.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-54253?

It affects 1 product.


Products: Adobe Experience Manager Forms.

## How do I fix CVE-2025-54253?

No fix has been published for CVE-2025-54253 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Nov 2025.

## Is CVE-2025-54253 being exploited?

Yes. Attackers have exploited CVE-2025-54253 in the wild since at least 15 Oct 2025.

Public exploit code:

- Breaking down CVE-2025-54253 — an Adobe AEM-Forms exploit path from XXE to full remote code execution and its real-world impact. (github_poc): https://github.com/AdityaBhatt3010/CVE-2025-54253-Inside-the-Adobe-AEM-Forms-Zero-Day
- CVE-2025-54253  |  CVE-2025-54254 | Adobe Experience Manager Forms XXE → RCE Framework (github_poc): https://github.com/zoomdbz/AEMPWN
- Simulated PoC for CVE-2025-54253: Adobe AEM OGNL Injection Vulnerability (github_poc): https://github.com/Shivshantp/CVE-2025-54253-Exploit-Demo

## Other vulnerabilities in Adobe Experience Manager

- [CVE-2025-54254](https://insights.sbomify.com/CVE-2025-54254/): Adobe Experience Manager | Improper Restriction of XML External Entity Reference ('XXE') (CWE-611) (high 8.6)
- [CVE-2017-3067](https://insights.sbomify.com/CVE-2017-3067/): Information disclosure in Adobe Experience Manager Forms 6.2, 6.1, 6.0 (high 7.5)
- [CVE-2019-8089](https://insights.sbomify.com/CVE-2019-8089/): Cross-site scripting in Adobe Experience Manager Forms (medium 6.1)
- [CVE-2019-7129](https://insights.sbomify.com/CVE-2019-7129/): Cross-site scripting in Adobe Experience Manager Forms (medium 6.1)
- [CVE-2016-6934](https://insights.sbomify.com/CVE-2016-6934/): Cross-site scripting in Adobe Experience Manager Forms 6.2 and earlier, LiveCycle 11.0.1, LiveCycle 10.0.4 (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54253 and fix it if it is affected.

What it is: CVE-2025-54253 is a critical missing authorization vulnerability in Adobe Experience Manager, published on 5 Aug 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-54253 in the wild since at least 15 Oct 2025.

Affected product: Adobe Experience Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-54253/ (Markdown: https://insights.sbomify.com/CVE-2025-54253/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54253
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54253
- OSV: https://osv.dev/vulnerability/CVE-2025-54253

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54253/
Summaries are generated and may contain mistakes; the official description above is the record.