# CVE-2025-3152: caipeichao ThinkOX Search search.html cross site scripting

> Remote attackers can inject malicious scripts via the search keywords parameter in ThinkOX, 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`)
- **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:** 3 Apr 2025
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-8gw7-rgf3-h6qx

## What is CVE-2025-3152?

CVE-2025-3152 is a medium-severity cross-site scripting vulnerability in caipeichao ThinkOX, published on 3 Apr 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 vulnerability classified as problematic has been found in caipeichao ThinkOX 1.0. This affects an unknown part of the file /ThinkOX-master/index.php?s=/Weibo/Index/search.html of the component Search. The manipulation of the argument keywords leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

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-3152?


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

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

## Is CVE-2025-3152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3152 is a medium-severity cross-site scripting vulnerability in caipeichao ThinkOX, published on 3 Apr 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-3152 exists.

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

## Sources

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

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