CVE-2025-49493VulnerabilityPublished 30 Jun 2025Updated 24 Sep 2025

CVE-2025-49493: Akamai CloudTest · XML External Entity (XXE)

Affects Akamai CloudTestSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.1% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jun 2025
Detectable: evidence found.
nuclei template: Akamai CloudTest < 60 2025.06.02 - XML External Entity (XXE)
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Akamai CloudTest	Affected =0	Fixed in–

AI-suggested

European organizations should immediately assess their use of Akamai CloudTest and identify any instances running versions prior to 60 2025.06.02 (12988). Until an official patch is released, organizations should implement the following mitigations: 1) Restrict network access to CloudTest instances, limiting exposure to trusted IP addresses and internal networks only. 2) Employ XML parser configurations that disable external entity processing or use secure XML parsing libraries that prevent XXE attacks. 3) Monitor logs for suspicious XML payloads or unexpected file access attempts. 4) Conduct internal code and configuration reviews to ensure no other XML processing components are vulnerable to XXE. 5) Prepare for rapid patch deployment once Akamai releases an official fix. 6) Educate development and testing teams about the risks of XXE and safe XML handling practices. These targeted actions go beyond generic advice by focusing on immediate containment and secure XML parsing configurations specific to the CloudTest environment.

Description

Akamai CloudTest before 60 2025.06.02 (12988) allows file inclusion via XML External Entity (XXE) injection.

Impact

For European organizations using Akamai CloudTest, this vulnerability poses a risk of sensitive information disclosure. Since CloudTest is often used in development and testing environments, attackers exploiting this XXE flaw could gain access to internal configuration files, credentials, or proprietary data, which could facilitate further attacks or intellectual property theft. The confidentiality breach could undermine compliance with GDPR and other data protection regulations, leading to legal and financial repercussions. Although the vulnerability does not directly affect system integrity or availability, the exposure of sensitive data could indirectly impact operational security and trust. Organizations relying on CloudTest for critical testing workflows may also face disruption if exploitation leads to the need for emergency remediation or forensic investigation. The lack of known exploits reduces immediate risk, but the ease of exploitation (no privileges or user interaction required) means that attackers could quickly develop exploits once details become public.

CWE-611Improper Restriction of XML External Entity Reference (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Implementation · System Configuration
Many XML parsers and validators can be configured to disable external entity expansion.
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.2 (opens in a new tab)
Attack patterns
Data Serialization External Entities Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Sep 2025, 00:14 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-611

Technical details

References

Community reviews

Related threats