# CVE-2025-24527: Missing authorization in Enterprise Application Access

> An admin can execute debug commands on another tenant's connector if they know its GUID, leading to potential code execution and privilege escalation.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2025
- **Updated:** 24 Feb 2025
- **Also known as:** GHSA-9r3r-662w-7j3w

## What is CVE-2025-24527?

CVE-2025-24527 is a high-severity missing authorization vulnerability in Akamai Enterprise Application Access, published on 29 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Akamai Enterprise Application Access (EAA) before 2025-01-17. If an admin knows another tenant's 128-bit connector GUID, they can execute debug commands on that connector.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

No fix has been published for CVE-2025-24527 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24527 being exploited?

There is no known exploitation of CVE-2025-24527 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24527 is a high-severity missing authorization vulnerability in Akamai Enterprise Application Access, published on 29 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24527 in the wild and no public exploit code.

Affected product: Akamai Enterprise Application Access. 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-24527/ (Markdown: https://insights.sbomify.com/CVE-2025-24527/index.md)
```

## Sources

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

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