# CVE-2020-37225: Powie's WHOIS Domain Check 0.9.31 Persistent Cross-Site Scripting

> Authenticated attackers can inject JavaScript into admin settings to execute code and escalate privileges in the WHOIS Domain Check plugin.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/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:** 13 May 2026
- **Updated:** 24 May 2026
- **Also known as:** GHSA-73xm-g8c2-75wg

## What is CVE-2020-37225?

CVE-2020-37225 is a medium-severity cross-site scripting vulnerability in Powie WHOIS Domain Check, published on 13 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Powie's WHOIS Domain Check 0.9.31 contains a persistent cross-site scripting vulnerability that allows authenticated attackers to inject arbitrary JavaScript by exploiting unsanitized input fields in plugin settings. Attackers can submit malicious payloads through textarea and input elements in the pwhois_settings.php configuration page to execute JavaScript in the admin context and escalate privileges.

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

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


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

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

## Is CVE-2020-37225 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37225 is a medium-severity cross-site scripting vulnerability in Powie WHOIS Domain Check, published on 13 May 2026. 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-2020-37225 exists.

Affected product: Powie WHOIS Domain Check. 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-37225/ (Markdown: https://insights.sbomify.com/CVE-2020-37225/index.md)
```

## Sources

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

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