# CVE-2025-30143: Cross-site scripting in App & API Protector

> Akamai App & API Protector fails to block XSS attacks exploiting JavaScript variable assignments to built-in functions, allowing potential script injection.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-rmhf-8c8c-36j6

## What is CVE-2025-30143?

CVE-2025-30143 is a medium-severity cross-site scripting vulnerability in Akamai App & API Protector, published on 17 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rule 3000216 (before version 2) in Akamai App & API Protector (with Akamai ASE) before 2024-12-10 does not properly consider JavaScript variable assignment to built-in functions and properties.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2025-30143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30143 is a medium-severity cross-site scripting vulnerability in Akamai App & API Protector, published on 17 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30143 in the wild and no public exploit code.

Affected product: Akamai App & API Protector. 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-30143/ (Markdown: https://insights.sbomify.com/CVE-2025-30143/index.md)
```

## Sources

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

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