# CVE-2025-61183: VaahCMS is vulnerable to XSS through its Avatar Upload endpoint

> A remote attacker can execute arbitrary code via a cross-site scripting vulnerability in the user avatar upload method of VaaHCMS.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2025
- **Updated:** 8 Oct 2025
- **Also known as:** GHSA-q769-phqg-263r

## What is CVE-2025-61183?

CVE-2025-61183 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross Site Scripting in vaahcms v.2.3.1 allows a remote attacker to execute arbitrary code via upload method in the storeAvatar() method of UserBase.php

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

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

2 open source packages ship an affected version, including webreinvent/vaahcms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `webreinvent/vaahcms` | Packagist | All versions to 2.3.1 | None |
| `webreinvent/vaahcms` | Packagist | All versions to 2.3.1 | None |

Products: Webreinvent Vaahcms.

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

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

## Is CVE-2025-61183 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61183 exists.

Public exploit code:

- https://github.com/thawphone/CVE-2025-61183 (github_poc): https://github.com/thawphone/CVE-2025-61183

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61183 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61183 exists.

Affected packages and fixed versions:
- webreinvent/vaahcms (Packagist): affected all versions up to 2.3.1; no fix listed
- webreinvent/vaahcms (Packagist): affected all versions up to 2.3.1; no fix listed

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

## Sources

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

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