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

> Cross-site scripting in WP Smart CRM allows attackers to inject malicious scripts via multiple input fields, potentially compromising user sessions.

- **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:** 14 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6rjj-pr45-qcv8

## What is CVE-2020-25375?

CVE-2020-25375 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 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

Wordpress Plugin Store / SoftradeWeb SNC WP SMART CRM V1.8.7 is affected by: Cross Site Scripting via the Business Name field, Tax Code field, First Name field, Address field, Town field, Phone field, Mobile field, Place of Birth field, Web Site field, VAT Number field, Last Name field, Fax field, Email field, and Skype field.

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

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

It affects 1 product.


Products: Softrade Wp Smart Crm \& Invoices.

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

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

## Is CVE-2020-25375 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25375 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 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-25375 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-25375/ (Markdown: https://insights.sbomify.com/CVE-2020-25375/index.md)
```

## Sources

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

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