# CVE-2025-9646: O2OA calendarConfig cross site scripting

> Remote attackers can inject malicious scripts via the toMonthViewName parameter in O2OA, potentially leading to session hijacking or code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-hj93-8xvj-w9rj

## What is CVE-2025-9646?

CVE-2025-9646 is a medium-severity cross-site scripting vulnerability in O2OA, published on 29 Aug 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 security flaw has been discovered in O2OA up to 10.0-410. This vulnerability affects unknown code of the file /x_organization_assemble_personal/jaxrs/definition/calendarConfig. The manipulation of the argument toMonthViewName results in cross site scripting. The attack can be launched remotely. The exploit has been released to the public and may be exploited. The vendor replied in the GitHub issue (translated from simplified Chinese): "This issue will be fixed in the new version."

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Zoneland O2oa.

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

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

## Is CVE-2025-9646 being exploited?

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

## Other vulnerabilities in O2OA

- [CVE-2023-47418](https://insights.sbomify.com/CVE-2023-47418/): Code injection in n/a (critical 9.8)
- [CVE-2022-22916](https://insights.sbomify.com/CVE-2022-22916/): Code injection in n/a (critical 9.8)
- [CVE-2024-37777](https://insights.sbomify.com/CVE-2024-37777/): Code injection in n/a (high 8.8)
- [CVE-2025-22994](https://insights.sbomify.com/CVE-2025-22994/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-35591](https://insights.sbomify.com/CVE-2024-35591/): File upload in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9646 is a medium-severity cross-site scripting vulnerability in O2OA, published on 29 Aug 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-9646 exists.

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

## Sources

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

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