Skip to main content
CVE-2025-54249VulnerabilityPublished

CVE-2025-54249: Adobe Experience Manager · Server-Side Request Forgery (SSRF)

Affects Adobe Experience ManagerSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.9% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Sep 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Adobe Adobe Experience ManagerAffected
  • =0
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations using Adobe Experience Manager should: 1) Monitor Adobe’s official security advisories closely for patches or updates addressing CVE-2025-54249 and apply them promptly once available. 2) Implement strict network segmentation and firewall rules to limit the server’s ability to make outbound requests to only trusted internal and external endpoints, reducing the SSRF attack surface. 3) Employ web application firewalls (WAFs) with rules designed to detect and block SSRF attack patterns targeting AEM. 4) Review and harden access controls to ensure that only necessary users have low-privileged access that could be leveraged in this attack. 5) Conduct internal audits and penetration tests focusing on SSRF vectors within AEM deployments to identify and remediate potential exploitation paths. 6) Log and monitor server-side request activity for unusual or unauthorized outbound requests that could indicate exploitation attempts. 7) Consider implementing application-layer request validation and allowlisting to restrict URLs or IPs that the server can access. These measures go beyond generic advice by focusing on network-level controls, monitoring, and access management specific to the nature of SSRF in AEM environments.

Description

Adobe Experience Manager versions 6.5.23.0 and earlier are affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to manipulate server-side requests and bypass security controls allowing unauthorized read access.

References

Community reviews

Loading reviews…