# CVE-2025-66824: Cross-site scripting in n/a

> Attackers can inject scripts into the meeting location field to achieve full account takeover when victims view the conference info page.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-wc9p-rvp2-mc4r

## What is CVE-2025-66824?

CVE-2025-66824 is a high-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Stored Cross-Site Scripting (XSS) vulnerability exists in the Meeting location field of the Create/Edit Conference functionality in TrueConf Server v5.5.2.10813. The injected payload is stored via the meeting_room parameter and executed when users visit the Conference Info page, allowing attackers to achieve full Account Takeover (ATO). This issue is caused by improper sanitization of user-supplied input in the meeting_room field.

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

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

It affects 1 product.


Products: Trueconf Trueconf Server.

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

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

## Is CVE-2025-66824 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-72530](https://insights.sbomify.com/CVE-2026-72530/): TrueConf Server Code Injection (critical 9.5, exploited in the wild)
- [CVE-2026-72529](https://insights.sbomify.com/CVE-2026-72529/): TrueConf Server Missing Authentication for Critical Function (critical 9.3, exploited in the wild)
- [CVE-2025-66834](https://insights.sbomify.com/CVE-2025-66834/): Code injection in n/a (high 7.3)
- [CVE-2017-20120](https://insights.sbomify.com/CVE-2017-20120/): TrueConf Server cross-site request forgery (medium 4.3)
- [CVE-2025-66823](https://insights.sbomify.com/CVE-2025-66823/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66824 is a high-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2025. Any signed-in user can exploit it over the network, 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-66824 exists.

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

## Sources

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

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