CVE-2025-54253 · Published 5 Aug 2025
Adobe Experience Manager (AEM) Forms
On CISA's KEV list 71 days after disclosure; 7 public exploits.
Adobe Experience Manager Forms in JEE contains an unspecified vulnerability that allows for arbitrary code execution.
CISA required action (federal due date 5 Nov 2025): Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Signals
- KEV, exploited in the wild
- yes, added 15 Oct 2025, due 5 Nov 2025
- EPSS, 30-day forecast
- 81%, 100th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 5 Aug 2025 to today
- Disclosed
- First PoC+1 d
- KEV+70 d
70 days from the first proof of concept to the KEV listing
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 7 known · links only
GitHub PoCs 7Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars7
- AdityaBhatt3010/CVE-2025-54253-Inside-the-Adobe-AEM-Forms-Zero-Day10 stars
Trust ok 85 · 1 flag
- no source (no_source)
Breaking down CVE-2025-54253 — an Adobe AEM-Forms exploit path from XXE to full remote code execution and its real-world impact.
created 4 Nov 2025
- zoomdbz/AEMPWNTrust ok 1004 stars
CVE-2025-54253 | CVE-2025-54254 | Adobe Experience Manager Forms XXE → RCE Framework
created 10 Feb 2026
- Shivshantp/CVE-2025-54253-Exploit-DemoTrust ok 1001 stars
Simulated PoC for CVE-2025-54253: Adobe AEM OGNL Injection Vulnerability
created 6 Aug 2025
- akujedanjedon/CVE-2025-54253-Exploit-DemoNot checked
first seen by skopnix 18 Oct 2026
- B1ack4sh/Blackash-CVE-2025-54253Not checked
first seen by skopnix 18 Oct 2026
- barbaraeivyu/CVE-2025-54253-eNot checked
first seen by skopnix 18 Oct 2026
- jm7knz/CVE-2025-54253-Exploit-DemoNot checked
first seen by skopnix 18 Oct 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.