# CVE-2020-25071: Cross-site scripting in n/a

> Cross-site scripting vulnerability in Nifty Project Management allows attackers to inject scripts via task creation, potentially leading to code execution.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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:** 15 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p7cq-h6rv-rjw6

## What is CVE-2020-25071?

CVE-2020-25071 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Nifty Project Management Web Application 2020-08-26 allows XSS, via Add Task, that is rendered upon a Project Home visit. Note: It has been argued that this is not reproducible. "The original issue was that the task would be created and an alert would be shown on the screen. Now the task would be created, but the alert won't be executed as those attributes are now stripped.

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

## Which versions are affected by CVE-2020-25071?

It affects 1 product.


Products: Niftypm Nifty.

## How do I fix CVE-2020-25071?

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

## Is CVE-2020-25071 being exploited?

There is no known exploitation of CVE-2020-25071 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25071 and fix it if it is affected.

What it is: CVE-2020-25071 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-25071 in the wild and no public exploit code.

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

## Sources

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

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