# CVE-2025-55135: Cross-site scripting in Agora

> Attackers can execute arbitrary scripts via malicious SVG profile pictures in Agora, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-jcj4-g9w3-h34q

## What is CVE-2025-55135?

CVE-2025-55135 is a medium-severity cross-site scripting vulnerability in Agora, published on 7 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Agora Foundation Agora fall23-Alpha1 before 690ce56, there is XSS via a profile picture to server/controller/userController.js. Formats other than PNG, JPEG, and WEBP are permitted by server/routes/userRoutes.js; this includes SVG.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-55135 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55135 is a medium-severity cross-site scripting vulnerability in Agora, published on 7 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55135 in the wild and no public exploit code.

Affected product: Agora. 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-55135/ (Markdown: https://insights.sbomify.com/CVE-2025-55135/index.md)
```

## Sources

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

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