Threats / Adobe / CVE-2025-54253
CVE-2025-54253
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Adobe Experience Manager (AEM) Forms vulnerability
Adobe Experience Manager Forms in JEE contains an unspecified vulnerability enabling arbitrary code execution. The flaw is actively exploited in the wild.
Verdict
Today item — known-exploited.
An unspecified code execution vulnerability in Adobe Experience Manager Forms JEE deployment allows attackers to execute arbitrary code on affected systems. Active exploitation in the wild indicates immediate risk to deployed instances.
CISA KEV Yes · 2025-10-155EPSS 0.87989 (verify live)6CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
17 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-15).
Probability (EPSS)
EPSS 0.87989 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Adobe, Experience Manager (AEM) Forms. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-863 Incorrect Authorization — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 71 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify and target a vulnerable Adobe Experience Manager Forms JEE instance exposed to the network.
Business
Exposed AEM Forms instances become entry points for unauthorized access and system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the unspecified vulnerability to execute arbitrary code with the privileges of the AEM Forms process.
Business
Arbitrary code execution allows attackers to establish persistence, escalate privileges, and move laterally within the infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I gain control of the underlying application server and access sensitive data processed by AEM Forms.
Business
Confidentiality and integrity of customer data, forms submissions, and business processes are compromised.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by adobeCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.