# CVE-2025-3965: itwanger paicoding post cross site scripting

> Remote attackers can inject malicious scripts via the post content field in paicoding, 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:** 27 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-2cj8-639j-6rq5

## What is CVE-2025-3965?

CVE-2025-3965 is a medium-severity cross-site scripting vulnerability in itwanger paicoding, published on 27 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 has been found in itwanger paicoding 1.0.3 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /article/app/post. The manipulation of the argument content leads to cross site scripting. The attack can be launched 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-3965?

It affects 1 product.


Products: Itwanger Paicoding.

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

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

## Is CVE-2025-3965 being exploited?

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

## Other vulnerabilities in itwanger paicoding

- [CVE-2026-3286](https://insights.sbomify.com/CVE-2026-3286/): itwanger paicoding Image Save Endpoint ImageRestController.java save server-side request forgery (medium 5.3)
- [CVE-2025-3966](https://insights.sbomify.com/CVE-2025-3966/): itwanger paicoding Browsing History home information disclosure (medium 5.3)
- [CVE-2025-3967](https://insights.sbomify.com/CVE-2025-3967/): itwanger paicoding Article post improper authorization (medium 5.3)
- [CVE-2025-4839](https://insights.sbomify.com/CVE-2025-4839/): itwanger paicoding CrossUtil.java cross-domain policy (low 2.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3965 is a medium-severity cross-site scripting vulnerability in itwanger paicoding, published on 27 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-3965 exists.

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

## Sources

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

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